Docker provides a level of abstraction from host operating systems allowing people using different types of operating systems (Windows 11, OS X Mojave, Ubuntu 18.04, Windows 10, etc.) to run the same code in the same way. This can be thought of as a more sophisticated version of conda or venv and a more lightweight version of a virtual machine. A docker container is specified by a Dockerfile. One machine may have many containers and they will all be visibile with docker container ls --all no matter where you type it.
Git is used for version control and editing code in teams. Different branches may have different versions of a file so depending on what branch you are on, you may see a different version. If you change branches to one with a new Dockerfile, however, this will not change a container that has already been built. To see changes reflected, you will need to rebuild the container. If using VS Code's Remote - Containers extension, it should detect any changes and alert you if you need to rebuild.
SSH is a protocol for connecting to remote machines. You can ssh USERNAME@ADDRESS to connect to the machine at ADDRESS as the user USERNAME. You may build and connect to Docker containers on remote machines as machines as well
WSL allows Windows users to execute code and programs as if they were using a linux machine. VS Code's 'Remote - WSL' extension allows you to open code files through WSL and handles routing any commands through WSL for you. You can ssh to remote machine or build a container from WSL.
It is possible to connect to WSL, ssh to a remote machine, launch a container there, and connect to that container. It may be very confusing, but this is all just done to ensure when one person runs a python program the same things happens as when their teammate does.
error: cannot run ssh: No such file or directory
fatal: unable to forkFollow these instructions from the docs. Note that if you are using WSL2, follow the instructions for Linux, not Windows.
This issue still persists sometimes and is in progress.
If you are trying to reach a separate container using localhost, you should change to the service name in the compose file.
Docker by default runs as a root user. When you make a new file in a container it is owned by root. So outside the container in the repository root, you can sudo chown -R $USER: . This will briefly elevate your permissions to root (sudo), and change the ownership (chown) to the current user in the current directory ., and all sub directories recursively (-R).
Jupyter will append a token to the end of the URL that it creates to open a notebook. Sometimes these tokens cause problems — especially within Docker containers. Here are some things to try to resolve these issues:
-
Make sure that you are copying the entire URL, including the token at the end:
http://127.0.0.1:8888/lab?token=6887d01c692f993a2171524aba1927ff34b9003c29d5b737 -
Docker needs to have permissions to access the folders where any files are mounted. You can find these settings in
Settings » Resources » File Sharing. If you make changes here, you may need to restart your computer for them to take effect. -
Sometimes Docker processes can hang in the background and cause issues. Restarting helps here, too.
-
If you don't have need for the security of tokens and passwords and they are causing issues, you can bypass them in the Jupyter command:
--NotebookApp.token='' --NotebookApp.password=''
Different chip architectures can cause opaque problems when running certain tools in Docker containers. You can use the --platform flag with docker build or docker run commands to specify the platform of the image.
Here's an example running the broadband image specifiying the platform:
docker build . -t broadband --platform=linux/amd64
docker run --platform=linux/amd64 -p 8888:8888 -v ${PWD}:/tmp broadband
docker exec -it CONTAINER_NAME /bin/bash
docker container ls -all