Specifically, the storage driver in use is what controls how the layer stack, and that top "r/w" layer is managed. If you specify a volume that is provided by any volume driver (the default being a local directory which will bind-mount into the target location in your container filesystem), this volume is unrelated to the image layers, including the 'writable' topmost layer provided by the back-end storage driver in use in your Docker engine. To your first question, no, no volumes are created without -v being used (ignoring for the moment the fact that the Dockerfile format does have a VOLUME verb). Volumes and image layers are separate concepts in Docker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |