We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What happened:
$ dive build my-folder -t my-img:v0.1 Building image... [+] Building 0.1s (1/1) FINISHED docker:desktop-linux => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 2B 0.0s ERROR: failed to solve: failed to read dockerfile: open Dockerfile: no such file or directory View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/uqu79lpwm9igb05ztacitkdga cannot build image exit status 1
What you expected to happen:
$ dive build my-folder -t my-img:v0.1 Building image... [+] Building 0.6s (8/8) FINISHED docker:desktop-linux => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 134B 0.0s => [internal] load metadata for registry.access.redhat.com/ubi9/ubi-micro:latest 0.5s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [internal] load build context 0.0s => => transferring context: 7.67kB 0.0s => [1/4] FROM ............................... 0.0s => exporting to image 0.0s => => exporting layers 0.0s => => writing image sha256:34126ca8646db858da1aa321533b736829fec5bd7a763b4aefeb78d137afceff 0.0s => => naming to ......... 0.0s View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/721o2x2iq0eyjcpaxb2q83uv4 What's Next? View a summary of image vulnerabilities and recommendations → docker scout quickview Analyzing image... Building cache...
and displaying dive
How to reproduce it (as minimally and precisely as possible):
Having a Containerfile instead of a Dockerfile
Thanks to that Dive will be compliant with Containerfile instead (podman, buildah)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happened:
What you expected to happen:
and displaying dive
How to reproduce it (as minimally and precisely as possible):
Having a Containerfile instead of a Dockerfile
Thanks to that Dive will be compliant with Containerfile instead (podman, buildah)
The text was updated successfully, but these errors were encountered: