You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Configs uid, gid and mode is will not take effect with configs of type file #12270
changed the title [-][BUG] Configs uid, gid and mode is will not take effect with configs with type file[/-][+][BUG] Configs uid, gid and mode is will not take effect with configs of type file[/+]on Nov 5, 2024
This is a known limitation, as we use bind mounts to add config file inside container, and bind mount doesn't allow to override uid/gid/mode as seen by container
See #12251 for discussion to add support for this using an alternative approach
would make sense, feel free to propose some additional notes on https://github.com/docker/docs
But this page is a copy from github.com/compose-spec and as such not specific to Docker Compose, so hardly can have a dedicated section on limitations we have in this area. Anyway, Docker Compose will warn you about unsupported attribute when you run compose up command
Activity
[-][BUG] Configs uid, gid and mode is will not take effect with configs with type file[/-][+][BUG] Configs uid, gid and mode is will not take effect with configs of type file[/+]ndeloof commentedon Nov 6, 2024
This is a known limitation, as we use bind mounts to add config file inside container, and bind mount doesn't allow to override uid/gid/mode as seen by container
See #12251 for discussion to add support for this using an alternative approach
meldafrawi commentedon Nov 6, 2024
@ndeloof is a change in docs required here?
ndeloof commentedon Nov 7, 2024
would make sense, feel free to propose some additional notes on https://github.com/docker/docs
But this page is a copy from github.com/compose-spec and as such not specific to Docker Compose, so hardly can have a dedicated section on limitations we have in this area. Anyway, Docker Compose will warn you about unsupported attribute when you run
compose upcommand