The documentation is wrong or the developers are wrong.

[quarky42]

Is this a docs issue?

• [X] My issue is about the documentation content or website

Type of issue

Information is incorrect

Description

Go read here: https://github.com/docker/compose/issues/9648

See how docker compose doesn't support uid, gid, or mode like the documentation says it does? The documentations says that these are supported for both configs and secrets blocks, but I have found out the hard way that the values are being ignored I'm Docker Compose.

Either the documents need to be updated to explain the limitations when using Docker Compose or the feature needs to be fixed (at least for Linux based containers) to support proper gui / user id parameters a d file permissions. The Docker Swarm deployment supports these parameters fully, but the Compose usage of the very same yml file results in vastly different behavior.

Location

https://docs.docker.com/compose/compose-file/compose-file-v3/

Suggestion

I really hope you can encourage the developers to get on this and actually fix it.

[docker-robot[bot]]

There hasn't been any activity on this issue for a long time. If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment. If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

[quarky42]

/remove-lifecycle stale comment

[quarky42]

Still an issue. Either need the documentation to reflect the realty of the limited functionality of docker compose versus the full implementation that is present when using the same yml file with Docker Swarm, or better yet, make Docker Compose support the permissions and ownership fully so that swarm services can be rapidly tested locally with better compose support.

[docker-robot[bot]]

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked