FAQ about Dev Containers
I see various volumes and properties in Docker after I created a dev container. What does each of them do?
After a dev container is created, the following volumes and properties appear in Docker:
jb_devcontainer_cache_xxx: this is a cached volume that contains all backend cashes in the
jb-devcontainer-features-xxx: if you use
devcontainer.jsonfile then all features are placed into such images.
Currently, the unnecessary images should be deleted manually.
jb_devcontainer_sources_xxx: if we use
git clonethen all sources are cloned into this volume using helper container (based on alpine/git image).
How do I add more log information when creating a dev container?
Add tothe following strings:
How do I understand that my SSH connection was successful for creating a remote dev container using -ssh git clone?
Run the following command:
Check the following example:
Why is the alpine/git image pulled during dev container creation?
We create a helper container based on the small
alpine/git image, which contains some of the required tools or libraries, for example git or the SSH client. We need that to clone the repository that can be absent in the image used for a dev container creation.
Why don't you use the Create Dev Container and Mount Sources option for the SSH Docker connections?
If we already have all the sources locally, there is no need to use such a complicated and slow method like Docker via SSH.