nerdctl built images, without a tag don't show up when running nerdctl images command

[vsiravar]

When I build an image using nerdctl build . without -t/--tag option, the image does not show up on running nerdctl images

Steps to reproduce this issue.

siravara@lima-default:/Users/siravara/vishwas-tests/temp$ nerdctl --version 
nerdctl version 0.23.0

siravara@lima-default:/Users/siravara/vishwas-tests/temp$ cat Dockerfile 
FROM public.ecr.aws/docker/library/debian:latest
RUN ["echo", "hello"]

siravara@lima-default:/Users/siravara/vishwas-tests/temp$ nerdctl build .
[+] Building 1.3s (6/6) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 108B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for public.ecr.aws/docker/library/debian:lat 1.2s
=> [1/2] FROM public.ecr.aws/docker/library/debian:latest@sha256:3e82b1a 0.0s
=> => resolve public.ecr.aws/docker/library/debian:latest@sha256:3e82b1a 0.0s
=> CACHED [2/2] RUN ["echo", "hello"] 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => exporting manifest sha256:ff79eb83771bf6c7639023cb0b17d605e7bcd40d 0.0s
=> => exporting config sha256:7b70ed5aa3f2e07dd403a065230f6d328603427bfd 0.0s

siravara@lima-default:/Users/siravara/vishwas-tests/temp$ nerdctl images 
REPOSITORY    TAG    IMAGE ID    CREATED    PLATFORM    SIZE    BLOB SIZE

Is this the intended behaviour, if so If you build an image, regardless of the output type, when would you expect it to not be included in nerdctl images?

[manugupt1]

How is your buildkit configured. I am not able to reproduce it locally.

Failed to connect to bus: No medium found
➜  tmp git:(master) ✗ nerdctl build .                      
[+] Building 2.2s (6/6) FINISHED                                                                                                            
 => [internal] load build definition from Dockerfile                                                                                   0.0s
 => => transferring dockerfile: 162B                                                                                                   0.0s
 => [internal] load .dockerignore                                                                                                      0.0s
 => => transferring context: 2B                                                                                                        0.0s
 => [internal] load metadata for public.ecr.aws/docker/library/debian:latest                                                           0.2s
 => [1/2] FROM public.ecr.aws/docker/library/debian:latest@sha256:3e82b1af33607aebaeb3641b75d6e80fd28d36e17993ef13708e9493e30e8ff9     0.0s
 => => resolve public.ecr.aws/docker/library/debian:latest@sha256:3e82b1af33607aebaeb3641b75d6e80fd28d36e17993ef13708e9493e30e8ff9     0.0s
 => CACHED [2/2] RUN echo "hello1"                                                                                                     0.0s
 => exporting to oci image format                                                                                                      2.0s
 => => exporting layers                                                                                                                0.0s
 => => exporting manifest sha256:f6863955f6f47c3ebbf8864602046d230c427d5a479bbda20cd89d522f5fa86d                                      0.0s
 => => exporting config sha256:0f5874371f25b8504021febba2c304cf42770d5a8bb703ae91d80710a773b236                                        0.0s
 => => sending tarball                                                                                                                 1.9s
unpacking overlayfs@sha256:f6863955f6f47c3ebbf8864602046d230c427d5a479bbda20cd89d522f5fa86d (sha256:f6863955f6f47c3ebbf8864602046d230c427d5a479bbda20cd89d522f5fa86d)...done
➜  tmp git:(master) ✗ nerdctl images 
REPOSITORY    TAG       IMAGE ID        CREATED           PLATFORM       SIZE         BLOB SIZE
overlayfs     <none>    f6863955f6f4    18 seconds ago    linux/amd64    135.0 MiB    52.5 MiB
➜  tmp git:(master) ✗ cat Dockerfile 
FROM public.ecr.aws/docker/library/debian:latest
RUN echo "hello1"%                                                                                                                          
➜  tmp git:(master) ✗ 

[vsiravar]

Thanks for getting back. I am using nerdctl that comes with lima (link). I start my lima instance with ubuntu guest, which is the default configuration for lima. I believe this is the configuration (link). What version of nerdctl are you running?

[manugupt1]

I am building out of master.

➜ tmp git:(master) ✗ nerdctl --debug build . has the output

DEBU[0000] stateDir: /run/user/1000/containerd-rootless 
DEBU[0000] rootless parent main: executing "/usr/bin/nsenter" with [-r/ -w/home/manu/go/src/github.com/containerd/nerdctl/tmp --preserve-credentials -m -n -U -t 3314 -F nerdctl --debug build .] 
DEBU[0000] Choosing the buildkit host "buildkit-default/buildkitd.sock", candidates=[buildkit-default/buildkitd.sock buildkit/buildkitd.sock] (in "/run/user/1000") 
DEBU[0000] Choosing the buildkit host "buildkit/buildkitd.sock", candidates=[buildkit-default/buildkitd.sock buildkit/buildkitd.sock] (in "/run/user/1000") 
DEBU[0000] Chosen buildkit host "unix:///run/user/1000/buildkit/buildkitd.sock" 
DEBU[0000] worker labels: map[org.mobyproject.buildkit.worker.containerd.namespace:buildkit org.mobyproject.buildkit.worker.containerd.uuid:3e889e45-10f7-42a9-a18a-a2d2d4609a64 org.mobyproject.buildkit.worker.executor:containerd org.mobyproject.buildkit.worker.hostname:fedora org.mobyproject.buildkit.worker.network:host org.mobyproject.buildkit.worker.snapshotter:overlayfs] 
DEBU[0000] running /usr/bin/buildctl [--addr=unix:///run/user/1000/buildkit/buildkitd.sock build --progress=auto --frontend=dockerfile.v0 --local=context=. --output=type=docker --local=dockerfile=/home/manu/go/src/github.com/containerd/nerdctl/tmp --opt=filename=Dockerfile] 
[+] Building 2.4s (6/6) FINISHED            

Can you share debug logs of build command

[vsiravar]

Here are the debug logs

DEBU[0000] stateDir: /run/user/504/containerd-rootless  
DEBU[0000] rootless parent main: executing "/usr/bin/nsenter" with [-r/ -w/Users/siravara/vishwas-tests/temp --preserve-credentials -m -n -U -t 1898 -F nerdctl build --debug .] 
DEBU[0000] Choosing the buildkit host "buildkit-default/buildkitd.sock", candidates=[buildkit-default/buildkitd.sock buildkit/buildkitd.sock] (in "/run/user/504") 
DEBU[0000] Chosen buildkit host "unix:///run/user/504/buildkit-default/buildkitd.sock" 
DEBU[0000] worker labels: map[org.mobyproject.buildkit.worker.containerd.namespace:default org.mobyproject.buildkit.worker.containerd.uuid:8a34a203-5578-44f7-bdc6-f58cb3a0b32f org.mobyproject.buildkit.worker.executor:containerd org.mobyproject.buildkit.worker.hostname:lima-default org.mobyproject.buildkit.worker.network:host org.mobyproject.buildkit.worker.snapshotter:overlayfs] 
DEBU[0000] running /usr/local/bin/buildctl [--addr=unix:///run/user/504/buildkit-default/buildkitd.sock build --progress=auto --frontend=dockerfile.v0 --local=context=. --output=type=image,unpack=true --local=dockerfile=/Users/siravara/vishwas-tests/temp --opt=filename=Dockerfile] 
[+] Building 0.1s (6/6) FINISHED                                                
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
 => [internal] load build definition from Dockerfile                       0.0s
 => => transferring dockerfile: 108B                                       0.0s
 => [internal] load metadata for public.ecr.aws/docker/library/debian:lat  0.1s
 => [1/2] FROM public.ecr.aws/docker/library/debian:latest@sha256:3e82b1a  0.0s
 => => resolve public.ecr.aws/docker/library/debian:latest@sha256:3e82b1a  0.0s
 => CACHED [2/2] RUN ["echo", "hello"]                                     0.0s
 => exporting to image                                                     0.0s
 => => exporting layers                                                    0.0s
 => => exporting manifest sha256:ff79eb83771bf6c7639023cb0b17d605e7bcd40d  0.0s
 => => exporting config sha256:7b70ed5aa3f2e07dd403a065230f6d328603427bfd  0.0s

[manugupt1]

This is a bug when tags are not specified and buildkit options are --output=type=image,unpack=true
Is it possible to create an issue for the same,

[vsiravar]

Thanks for getting back, do you mean to create a bug for nerdctl or buildkit?

[manugupt1]

This should be fixed in nerdctl 1.0.1. Please check and let us know. Thanks!

[ginglis13]

Hi @manugupt1 , I ran into this issue (or similar) today. While the image appears in nerdctl images now, the image is overlayfs:<none> and cannot be referenced via other nerdctl commands...

$ nerdctl --version  # vended with Lima
nerdctl version 1.3.1

# Dockerfile
FROM fedora:38

Docker behavior:

$ docker build .
...
$ docker images
REPOSITORY                                                                                    TAG 
fedora                                                                                        38

nerdctl behavior:

$ nerdctl build .
...
$ nerdctl images
REPOSITORY                                                                                    TAG 
overlayfs                                                                                    <none>