Closed
Description
Hi,
My dockerfile
FROM busybox
RUN echo "hello world"
I make a build :
nerdctl build -t foo .
When I list my images i got a duplicate image:
./nerdctl images
WARN[0000] unparsable image name "overlayfs@sha256:f6af50796f7f2ee98a04bc5dbf721fb2ec4b6285f4f0cc4b0bd55e3f0f8249f0"
REPOSITORY TAG IMAGE ID CREATED SIZE
foo latest f6af50796f7f 2 seconds ago 748.4 KiB
f6af50796f7f 2 seconds ago 748.4 KiB
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
AkihiroSuda commentedon Apr 16, 2021
Buildkit version?
fahedouch commentedon Apr 16, 2021
@AkihiroSuda
buildkitd github.com/moby/buildkit v0.8.1-120-gc47972dc c47972dc5a9e2f4fc0a58d299b6f096161203fbb
fahedouch commentedon Apr 16, 2021
same thing for
buildkitd github.com/moby/buildkit v0.8.2 9065b18ba4633c75862befca8188de4338d9f94a
sacesare commentedon May 26, 2021
Same issue, images.go show "WARN[0000] unparsable image name", though it's perfectly legal IMHO,
docker - Restrictions regarding naming image
crictl images
show 16 images without warn/error.
nerdctl namespace ls
show "IMAGES" count 16*3=48.
nerdctl images
show 16 lines of
WARN[0000] unparsable image name "docker.io/bitnami/metallb-controller@sha256:e396c8737dd632ca84ab4d04fb8d7dfe47052a9a335db0610592744656d10c15"
...
and after that, 16*2=32 duplicated image names.
Teo90 commentedon Jul 22, 2021
I have the same problem!nerdctl v0.11.0 version
splooge commentedon Aug 3, 2021
Same problem here. I notice also that depending on the order of the arguments I get different results. For example
. -t nginx
creates 1 image while-t nginx .
creates 2.I'm using
nerdctl-full-0.11.0-linux-amd64.tar.gz
on an Ubuntu 20.04.2 fresh install. I also had the same problem on Arch. It happens on both rootful and rootless installs.The image size is also wrong (way too small)
rofafor commentedon Sep 11, 2021
I'm experiencing the same issue on my MacOS+lima setup. Depending on the order the parameter the tagging "fails" and there's always created a repo tag as
:
, that will give you warnings.nerdctl version
nerdctl info
buildkitd --version
nerdctl build . -t summerwind/actions-runner-controller:latest
:nerdctl build -t summerwind/actions-runner-controller:latest .
whg517 commentedon Sep 18, 2021
I have the same problem, when I build once with Dockerfile I get a new image and a warning that the image has no tag. This is true even if I use
-t foo:latest
. There were a lot of images without tags at build time. I don't know how to avoid this problem, but I think it might be a bug.AkihiroSuda commentedon Sep 28, 2021
Should be fixed in #357
Will be included in v0.12
nik-here commentedon Oct 9, 2021
OS: Ubuntu 21.04 (Default build with lima-vm)
nerdctl version 0.12.1
containerd version v1.5.7
buildkitd github.com/moby/buildkit v0.9.1 966bcf4aa3ef397a9d6025fade18f2d59a5bf29d
Dockerfile
When I build an image without the "-t" flag, the image is build successfully. However when I use "nerdctl images", I get the the warning / output: