docker-compose up creates directories on host system

[strk]

Running docker-compose up results in creation of directories specified via volumes directive on the host system. I think it would be better to error out if the host directory does not exist.

[strk]

besides, the directories are created by the "root" user, even if docker-compose up was called by an unprivileged user (other than being allowed to use the docker sockets)

[dnephin]

The directories are created by docker engine, not by compose itself, so this change would need to be made in the engine.

#16072 was the only related issue I could find , but it's for named volumes, not host volumes.

@thaJeztah do you know if there is any talk of this?

[thaJeztah]

Yes, we marked that "feature" as deprecated in 1.9, and it's targeted for removal in 1.11; https://github.com/docker/docker/blob/master/docs/deprecated.md#auto-creating-missing-host-paths-for-bind-mounts

Auto-creating missing host paths for bind mounts

Deprecated in Release: v1.9

Target for Removal in Release: 1.11

When creating a container with a bind-mounted volume-- docker run -v /host/path:/container/path -- docker was automatically creating the /host/path if it didn't already exist.

This auto-creation of the host path is deprecated and docker will error out if the path does not exist.

[dnephin]

Excellent. Closing this issue since it's being fixed by engine.

[dnephin]

Thanks @thaJeztah !

[strk]

Thanks everyone!

[mitar]

Nooo. This was great feature. How can one then make sure paths exist if they do not yet? You have to wrap docker-compose then into a script?

[mitar]

I think this signals well a need for the hooks: #1341

[verglor]

Hi @dnephin and @thaJeztah, this was un-deprecated so the problem still exists.
It was solved by a new --mount flag instead of --volume (see #13121).
Is it possible to use this new flag for mounting volumes in docker-comopse ?
Can we reopen this issue, if it is not possible yet ?

[thaJeztah]

@verglor If I'm not mistaken, the "long form" volumes syntax will use the mount API, thus not create local directories (unless the daemon is too old to support that API); see #5490

[michaelarnauts]

I'm not sure if there is an existing issue for the mount syntax in docker-compose. There are a lot of issues that specify "mount", but most handle issues with the volumes.

[thaJeztah]

The "volumes" key in the compose-file is used both for (named) "volumes" and for bind-mounts (if you specify a host path instead of a volume name, or, in the long-form when specifying type: bind). Using the long form syntax should use the mount API, which prevents paths on the host from being created by the daemon;

    volumes:
      - type: bind
        source: ./some/path/on/host
        target: /some/path/in/container