crazy-max
commented
5 months ago Do you have full build logs and full invoked command as well please?
Open nijave opened 5 months ago
crazy-max
commented
5 months ago Do you have full build logs and full invoked command as well please?
nijave
commented
5 months ago Do you have full build logs and full invoked command as well please?
Full command is in reproduce. There are no build logs
env -i GIT_COMMIT=318711e90f90a258e5edbb7ad7d66b25f1e095f7 __UPSTREAM_IMAGE_IDS= /usr/local/bin/docker -D buildx build --output=type=docker --pull=False --tag platform:redshift-db-init-latest --tag platform:redshift-db-init-318711e90f90a258e5edbb7ad7d66b25f1e095f7 --build-arg GIT_COMMIT --file redshift-db-init/Dockerfile .
unknown flag: --output
See 'docker --help'.
Usage: docker [OPTIONS] COMMAND
A self-sufficient runtime for containers
Common Commands:
run Create and run a new container from an image
exec Execute a command in a running container
ps List containers
build Build an image from a Dockerfile
pull Download an image from a registry
push Upload an image to a registry
images List images
login Log in to a registry
logout Log out from a registry
search Search Docker Hub for images
version Show the Docker version information
info Display system-wide information
Management Commands:
builder Manage builds
container Manage containers
context Manage contexts
image Manage images
manifest Manage Docker image manifests and manifest lists
network Manage networks
plugin Manage plugins
system Manage Docker
trust Manage trust on Docker images
volume Manage volumes
Swarm Commands:
swarm Manage Swarm
Commands:
attach Attach local standard input, output, and error streams to a running container
commit Create a new image from a container's changes
cp Copy files/folders between a container and the local filesystem
create Create a new container
diff Inspect changes to files or directories on a container's filesystem
events Get real time events from the server
export Export a container's filesystem as a tar archive
history Show the history of an image
import Import the contents from a tarball to create a filesystem image
inspect Return low-level information on Docker objects
kill Kill one or more running containers
load Load an image from a tar archive or STDIN
logs Fetch the logs of a container
pause Pause all processes within one or more containers
port List port mappings or a specific mapping for the container
rename Rename a container
restart Restart one or more containers
rm Remove one or more containers
rmi Remove one or more images
save Save one or more images to a tar archive (streamed to STDOUT by default)
start Start one or more stopped containers
stats Display a live stream of container(s) resource usage statistics
stop Stop one or more running containers
tag Create a tag TARGET_IMAGE that refers to SOURCE_IMAGE
top Display the running processes of a container
unpause Unpause all processes within one or more containers
update Update configuration of one or more containers
wait Block until one or more containers stop, then print their exit codes
Global Options:
--config string Location of client config files (default ".docker")
-c, --context string Name of the context to use to connect to the daemon (overrides DOCKER_HOST env var and default context set with "docker context use")
-D, --debug Enable debug mode
-H, --host list Daemon socket to connect to
-l, --log-level string Set the logging level ("debug", "info", "warn", "error", "fatal") (default "info")
--tls Use TLS; implied by --tlsverify
--tlscacert string Trust certs signed only by this CA (default ".docker/ca.pem")
--tlscert string Path to TLS certificate file (default ".docker/cert.pem")
--tlskey string Path to TLS key file (default ".docker/key.pem")
--tlsverify Use TLS and verify the remote
-v, --version Print version information and quit
Run 'docker COMMAND --help' for more information on a command.
For more help on how to use Docker, head to https://docs.docker.com/go/guides/Semi-related, it seems buildx config problems might be propagating as as various unknown flag errors https://github.com/docker/for-mac/issues/6928
Description
When
HOMEenvironment variable isn't set,buildxfails with a confusing error message aboutunknown flag: --outputReproduce
Run Docker without
HOMEset (env -i)Expected behavior
At the very least, a better error message. I assume this is used in some sort of config lookup.
Ideally allow falling back to an alternative method to match how Linux works (Docker on Linux seems work without HOME set)
docker version
docker info
Diagnostics ID
17B2BE18-161E-4E41-8B11-DF9220B867D7/20240326124035
Additional Info
pantsbuild tool attempts to runDockerin a minimal sandbox which is where this issue was discovered https://github.com/pantsbuild/pants/issues/20605