While it is known that file secrets cannot have their ownership / permissions set via service level secrets, it appears that environment secrets can, yet the warning about said ownership / permissions being ignored is displayed.
Steps To Reproduce
Set a secret from an environment variable and attempt to modify its uid, gid, and mode via service-level secrets
Run docker compose and display the uid, gid, and mode of the secret, noting the incorrect warning about them not being set
$ MY_SECRET=success docker compose run --rm my-service
WARN[0000] secrets `uid`, `gid` and `mode` are not supported, they will be ignored
-rwxr-xr-- 1 10 20 7 Jul 23 20:40 /run/secrets/my-secret
Description
While it is known that file secrets cannot have their ownership / permissions set via service level secrets, it appears that environment secrets can, yet the warning about said ownership / permissions being ignored is displayed.
Steps To Reproduce
Compose Version
Docker Environment
Anything else?
No response