As discussed in Docker Community Slack --quiet in docker buildx build command return an error (from a code point of view), a message telling that quiet is not implemented that stop the build process.
That implementation cause some script to failed when used in combination of docker build aliasing.
Reproducing
- Install buildx
- Set buildx as default builder
- Run
docker build -q . and you will get the message quiet currently not implemented and no build
Expecting result
From my opinion, --quiet flag absence should not be a blocker.
When running docker build -q . we should have a warning, then the build still continue.
As discussed in Docker Community Slack
--quietindocker buildx buildcommand return an error (from a code point of view), a message telling that quiet is not implemented that stop the build process.That implementation cause some script to failed when used in combination of
docker buildaliasing.Reproducing
docker build -q .and you will get the messagequiet currently not implementedand no buildExpecting result
From my opinion,
--quietflag absence should not be a blocker.When running
docker build -q .we should have a warning, then the build still continue.