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
secrets.NPM_TOKEN Additional property content is not allowed
This error does not happen on 4.32 (with compose version 2.28.1). It also seems to only happen for environment variables that are set in the terminal, using a random string for the secrets.npm_token.environment seems to work (though the build will fail because the environment variable does not have anything).
Description
The latest version of Docker For Mac, version 4.33, introduced a regression that broke the validation of Docker Build Secrets
Following these instructions, leads to the following error:
secrets.NPM_TOKEN Additional property content is not allowed
This error does not happen on 4.32 (with compose version 2.28.1). It also seems to only happen for environment variables that are set in the terminal, using a random string for the
secrets.npm_token.environment
seems to work (though the build will fail because the environment variable does not have anything).Reproduce
Create a compose file like so:
Run
docker compose up
ordocker compose build
Expected behavior
docker compose up
should work with build secrets from the environment.docker version
Client: Version: 27.1.1 API version: 1.46 Go version: go1.21.12 Git commit: 6312585 Built: Tue Jul 23 19:54:12 2024 OS/Arch: darwin/arm64 Context: desktop-linux Server: Docker Desktop 4.33.0 (160616) Engine: Version: 27.1.1 API version: 1.46 (minimum version 1.24) Go version: go1.21.12 Git commit: cc13f95 Built: Tue Jul 23 19:57:14 2024 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.7.19 GitCommit: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41 runc: Version: 1.7.19 GitCommit: v1.1.13-0-g58aa920 docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Diagnostics ID
9F7237CF-66DA-46E1-A31A-755ECDE6E436/20240731154007
Additional Info
No response
The text was updated successfully, but these errors were encountered: