Today, online education has become an integral part of the learning process. You shouldn’t need to restart the webserver or container.The constant changes in the technological landscape have led to developments in the education industry as well. Once you have updated the image and code, run make (or your other service) from devstack to apply the latest migrations. To fix this, make sure you have the latest images and latest code, similar to the steps for Missing Module. If the import error is still there, run make and then, from within the service container, run make requirementsĪfter doing this, it may Just Work or you may need to restart the service with make (run from devstack)Īnother error you may get if the code and the image are out of sync is sql or Django ORM errors about missing tables or models not having a certain field. If you are working on a branch, you may need to rebase it onto the latest master or main.įrom devstack, run make dev.up.lms and make To get the latest code, you can run git fetch & git pull from the head of the code repository. To update your image, you can run make from devstack. Replace lms with studio, credentials, discovery, etc. These instructions are written using the LMS as an example. To fix this, first make sure you have the latest images and the latest code. This usually happens because the code and the image are out of sync.

Occasionally, you’ll get errors like ‘Cannot import name Name from module xyz’. The current directory and sharing the real directory (or vice-versa) may work Resources - File Sharing section of the Docker preferences. Your actual devstack working directory matches the directory listed in the Slow sync times (up to an hour), it might be due to symlinks. If you have problems like shared directories not appearing as shared, or very That makes it easier to use the simpler git commands more effectivelyĪnd easier to use the more complicated git commands when you have to. com : openedx /įinally, if you regularly find yourself mystified by git, consider reading To fix this situation, change the owner back to yourself outside of the container by running: Within a container, that is the root user - so git operations Git pull, git changes the owner of the files that you pull to the user that runs Have pulled changes to the remote repository from within a container. Need to enter your root password when editing a file, you might If you notice that the ownership of some (maybe all) files have changed and you Docker is using lots of CPU time when it should be idle

Open edx slack