mirror of
https://github.com/docker/compose.git
synced 2026-11-17 13:45:39 +00:00
Pass `umask` to the engine as HostConfig.Umask when creating a container, so that the entrypoint, exec and healthcheck processes run with the requested file mode creation mask. The attribute is part of the container specification, so pre_start init containers, created the same way, get the umask of their service unless they declare their own. Engines older than API 1.56 (Docker Engine 29.8) silently ignore the field, which would run the container with the runtime's default umask without any notice: creating a container with a umask against such an engine now fails with an explicit error, like interface_name or image volumes do. The umask is part of the service configuration hash, so changing it recreates the container; the hash of every other configuration is untouched. Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com> |
||
|---|---|---|
| .. | ||
| compose.yaml | ||