The build commands above will use your local configuration, but pull
The build commands above will use your local configuration, but will pull
application code from the master branch of the application's repository. If you
would like to use code from another branch/tag/hash, modify the ``*_VERSION``
variable that lives in the ``ansible_overrides.yml`` file beside the
...
...
@@ -277,13 +283,15 @@ E-Commerce Service, you would modify ``ECOMMERCE_VERSION`` in
How do I create database dumps?
-------------------------------
We use database dumps to speed up provisioning and generally spend less time running migrations. These dumps should be
updated occasionally--when database migrations take a prolonged amount of time, or we want to incorporate changes that
require manual intervention. The process below details how to update the database dumps.
updated occasionally - when database migrations take a prolonged amount of time *or* we want to incorporate changes that
require manual intervention.
To update the database dumps:
1. Destroy and/or backup the data for your existing devstack so that you start with a clean slate.
2. Disable the loading of the existing database dumps during provisioning by commenting out any calls to ``load-db.sh``
in the provisioning scripts. This ensures that we start with a completely fresh database and incorporate any changes
that may have require some form of manual intervention for existing installations (e.g. drop/move tables).
in the provisioning scripts. This disabling ensures a start with a completely fresh database and incorporates any changes
that may have required some form of manual intervention for existing installations (e.g. drop/move tables).
3. Provision devstack with ``make provision``.
4. Dump the databases and open a pull request with your updates:
...
...
@@ -308,8 +316,8 @@ Alternatively, you can discard and rebuild the entire database for all
devstack services by re-running ``make dev.provision`` or
``make dev.sync.provision`` as appropriate for your configuration. Note that
if your branch has fallen significantly behind master, it may not include all
of the migrations included in the database dump used by provisioning. In
cases like this it's usually best to first rebase the branch onto master to
of the migrations included in the database dump used by provisioning. In these
cases, it's usually best to first rebase the branch onto master to
get the missing migrations.
...
...
@@ -358,7 +366,7 @@ starts, you have a few options:
reads ``...&& while true; do...`` could be changed to
``...&& pip install my-new-package && while true; do...``.
* In order to work on locally pip-installed repos like edx-ora2, first clone
them into ../src (relative to this directory). Then, inside your lms shell,
them into ``../src`` (relative to this directory). Then, inside your lms shell,
you can ``pip install -e /edx/src/edx-ora2``. If you want to keep this code
installed across stop/starts, modify ``docker-compose.yml`` as mentioned
above.
...
...
@@ -440,6 +448,7 @@ To detach from the container, you'll need to stop the container with:
make stop
or a manual Docker command to bring down the container:
.. code:: sh
docker kill $(docker ps -a -q --filter="name=edx.devstack.<container name>")
...
...
@@ -507,8 +516,7 @@ described above (Chrome is used by default).
Troubleshooting: General Tips
-----------------------------
If you are having trouble with your containers there are a few general steps
you can take to try to resolve.
If you are having trouble with your containers, this sections contains some troubleshooting tips.
Check the logs
~~~~~~~~~~~~~~
...
...
@@ -544,7 +552,7 @@ Clean the containers
~~~~~~~~~~~~~~~~~~~~
Sometimes containers end up in strange states and need to be rebuilt. Run
``make down`` to remove all containers and networks. This will NOT remove your
``make down`` to remove all containers and networks. This will **NOT** remove your
data volumes.
Start over
...
...
@@ -560,12 +568,13 @@ File ownership change
~~~~~~~~~~~~~~~~~~~~~
If you notice that the ownership of some (maybe all) files have changed and you
need to enter your root password when editing a file, that could be because you
have pulled changes the remote repository from within a container. While running
``git pull`` git changes the owner of the files that you pull to the user that runs
that command, and within a container that is the root user, hence git operations
need to enter your root password when editing a file, you might
have pulled changes to the remote repository from within a container. While running
``git pull``, git changes the owner of the files that you pull to the user that runs
that command. Within a container, that is the root user - so git operations
should be ran outside of the container.
To fix this change the owner back to yourself outside of the container by running:
To fix this situation, change the owner back to yourself outside of the container by running:
.. code:: sh
...
...
@@ -574,9 +583,9 @@ To fix this change the owner back to yourself outside of the container by runnin
Running LMS commands within a container
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Most of the ``paver`` commands require a settings flag, which if omitted defaults to
``devstack`` which is the settings flag for vagrant-based devstack instances. Therefor
if you run into issues running those command in a docker container you should append
Most of the ``paver`` commands require a settings flag. If omitted, the flag defaults to
``devstack``, which is the settings flag for vagrant-based devstack instances.
So if you run into issues running ``paver`` commands in a docker container, you should append
the ``devstack_docker`` flag. For example:
.. code:: sh
...
...
@@ -589,6 +598,8 @@ Resource busy or locked
While running ``make static`` within the ecommerce container you could get an error
saying:
.. code:: sh
Error: Error: EBUSY: resource busy or locked, rmdir '/edx/app/ecommerce/ecommerce/ecommerce/static/build/'
To fix this, remove the directory manually outside of the container and run the command again.
...
...
@@ -596,10 +607,10 @@ To fix this, remove the directory manually outside of the container and run the
No space left on device
~~~~~~~~~~~~~~~~~~~~~~~
If you see the error "no space left on device" on a Mac, it means Docker has run
If you see the error ``no space left on device`` on a Mac, Docker has run
out of space in its Docker.qcow2 file.
Here is an example error while running `make pull`:
Here is an example error while running ``make pull``:
.. code:: sh
...
...
@@ -608,15 +619,15 @@ Here is an example error while running `make pull`:
ERROR: failed to register layer: Error processing tar file(exit status 1): write /edx/app/edxapp/edx-platform/.git/objects/pack/pack-4ff9873be2ca8ab77d4b0b302249676a37b3cd4b.pack: no space left on device
make: *** [pull] Error 1
You can clean up data by running `docker system prune`, but you will first want
to run `make dev.up` so it doesn't delete stopped containers.
You can clean up data by running ``docker system prune``, but you will first want
to run ``make dev.up`` so it doesn't delete stopped containers.
Or, you can run the following commands to clean up dangling images and volumes:
.. code:: sh
docker image prune -f
docker volume prune -f (Be careful, this will remove your persistent data!)
docker volume prune -f # (Be careful, this will remove your persistent data!)
No such file or directory
~~~~~~~~~~~~~~~~~~~~~~~~~
...
...
@@ -626,12 +637,12 @@ While provisioning, some have seen the following error:
.. code:: sh
...
cwd = os.getcwdu()
cwd = os.getcwdu()
OSError: [Errno 2] No such file or directory
make: *** [dev.provision.run] Error 1
Everyone who has seen this has gotten past it, but we don't have a surefire way
to do so. Rebooting and restarting Docker do *not* seem to correct the issue. It
This issue can be worked around, but there's no guaranteed method to do so.
Rebooting and restarting Docker does *not* seem to correct the issue. It
may be an issue that is exacerbated by our use of sync (which typically speeds
up the provisioning process on Mac), so you can try the following:
...
...
@@ -654,9 +665,9 @@ While provisioning, some have seen the following error:
