-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] regression in compose secrets handling for include files between versions Docker version 26.1.4, build 5650f9b and 27.1.1, build 6312585 #12033
Comments
@ervin-pactum thank you for the details! pushed fix compose-spec/compose-go#669 , @ndeloof check please |
Bump, is there any problem to reproduce, or any other reason why this is still status/0-triage ? |
Bump, I am running into the same problem. When moving the secret definition one to one into the main file, the file is valid, but in the included file it is not. Also the PR seems only mildly related. |
Bump, It makes me downgrade Docker too often these days and creates a feeling that I am using a third party plugin of Docker not a Docker core product. Three minor versions with no fix nor addressing of problem 😞. Open to provide more examples, but I feel that upper post is explaining extremely well. |
The fix is here compose-spec/compose-go#669 , waiting for review/approve from @ndeloof |
This is a regression, therefore to my knowledge a good fix would find the commit where the bug started occurring and revert that change. |
@mTsBucy1 regression was introduced by a commit which is a fix for another issue. Considering a "revert on bug" strategy would prevent we move forward with Compose codebase, and is a pretty naive approach to software engineering imho |
@ndeloof what do you think about this fix compose-spec/compose-go#669 ? I can try to fix it using other ways if you don't like this one |
@idsulik sounds good to me, I don't think we have a better option with current compose-go architecture. |
Description
After upgrading docker desktop for mac from 4.31.0 (153195) to version 4.33.0 (160616) our compose based (development) setup stopped working with
secrets.one-token Additional property content is not allowed
and similar errors, when compose file using secret is included from another file. We are using ARM Mac on macOS Sonoma 14.5.Steps To Reproduce
create two compose files in peer directories
one
andtwo
:one/compose.yml:
(this configuration is valid according to
docker compose config --quiet
(exit 0) and starts if provided environment value without a problem:Follow by creating in peer folder (two/compose.yml):
this will also pass validation
docker compose config --quiet
is still zero. but attempt to start it$ access_token=access_token='secret value 2' docker compose up --force-recreate
will result in exit status code 15 with message:validating /Users/ervin/sandbox/compose-env-secrets-repro/two/compose.yml: secrets.one-secret-token Additional property content is not allowed
We did validate that on older docker desktop (4.31.0 (153195), Docker version 26.1.4, build 5650f9b) this works as expected, but (Docker Desktop 4.33.0 (160616) is not working anymore.
Compose Version
Docker Environment
Anything else?
one click reproduction, execute following as bash script:
The text was updated successfully, but these errors were encountered: