search

containers / bootc

Boot and upgrade via container images
https://containers.github.io/bootc/
Apache License 2.0
781 stars 84 forks source link

error: cannot build manifest: failed inspect image: exit status 125, stderr ... acquiring lock 0 for container 9e0ee552... file exists #785

Closed closet6 closed 2 months ago

closet6 commented 2 months ago

Following instructions from here: https://docs.fedoraproject.org/en-US/bootc/qemu-and-libvirt/

this is docker file: 

FROM quay.io/centos-bootc/centos-bootc:stream9
RUN touch /etc/file.txt

this is build script:

podman build -t bootcentos .
CONTAINER_IMAGE=localhost/bootcentos:latest
sudo podman run \
    --rm \
    -it \
    --privileged \
    --pull=newer \
    --security-opt label=type:unconfined_t \
    -v $(pwd)/output:/output \
    -v /var/lib/containers/storage:/var/lib/containers/storage \
    quay.io/centos-bootc/bootc-image-builder:latest \
    --type qcow2 \
    --local \
    $CONTAINER_IMAGE

when done I see this: podman images

[joe@centoshost bootc-vms]$ podman images
REPOSITORY                         TAG         IMAGE ID      CREATED         SIZE
localhost/bootcentos               latest      8cc6c6d06305  13 minutes ago  1.52 GB
quay.io/centos-bootc/centos-bootc  stream9     f64ef032ddac  16 hours ago    1.52 GB
quay.io/podman/hello               latest      5dd467fce50b  3 months ago    787 kB

I can run podman hello fine no problem.

Description: CentOS Stream 9

podman version 5.2.2

no docker installed

The error I get is the following:

[joe@centoshost bootc-vms]$ ./build.sh 
STEP 1/2: FROM quay.io/centos-bootc/centos-bootc:stream9
STEP 2/2: RUN touch /etc/file.txt
--> Using cache 8cc6c6d06305cb1e5d684f8e9523514d38c7faa7ab46d1d07e6e97b5ef56805b
COMMIT bootcentos
--> 8cc6c6d06305
Successfully tagged localhost/bootcentos:latest
8cc6c6d06305cb1e5d684f8e9523514d38c7faa7ab46d1d07e6e97b5ef56805b
[sudo] password for joe: 
Generating manifest manifest-qcow2.json
2024/09/11 22:29:59 error: cannot build manifest: failed inspect image: exit status 125, stderr:
time="2024-09-11T22:29:59Z" level=error msg="Refreshing container 17918797ec96d531f09db3fa7d26b237bc143e4f4e2f3ae4442be7c7af1afdba: acquiring lock 0 for container 17918797ec96d531f09db3fa7d26b237bc143e4f4e2f3ae4442be7c7af1afdba: file exists"
time="2024-09-11T22:29:59Z" level=error msg="Refreshing volume 5e9d4ded1e7ed3e10e29b65915769805368e92653e03ee91d7f44f108deabb32: acquiring lock 1 for volume 5e9d4ded1e7ed3e10e29b65915769805368e92653e03ee91d7f44f108deabb32: file exists"
time="2024-09-11T22:29:59Z" level=error msg="Refreshing volume 10abb114ca3486a9918ca1ac44068d02737f4e851976e26997227a743c7b9713: acquiring lock 2 for volume 10abb114ca3486a9918ca1ac44068d02737f4e851976e26997227a743c7b9713: file exists"
Error: localhost/bootcentos:latest: image not known

EDIT1: podman system reset did not help the problem

EDIT2: I tried the exact same thing on another centos9 machine and got a similar error but nothing about the Refreshing volume 3 times:

Trying to pull quay.io/centos-bootc/bootc-image-builder:latest...
Getting image source signatures
Copying blob d907935a8234 done   |
Copying blob d7daee9cdb60 done   |
Copying blob 999c1dd2d0b8 done   |
Copying config f64402d336 done   |
Writing manifest to image destination
Generating manifest manifest-qcow2.json
2024/09/12 00:00:50 error: cannot build manifest: failed inspect image: exit status 125, stderr:
Error: localhost/bootcentos:latest: image not known
[joe@centosmain bootc-vms]$ podman --version
podman version 5.2.2
[joe@centosmain bootc-vms]$ podman images
REPOSITORY                         TAG         IMAGE ID      CREATED        SIZE
localhost/bootcentos               latest      ac975cbdafb2  3 minutes ago  1.52 GB
quay.io/centos-bootc/centos-bootc  stream9     f64ef032ddac  18 hours ago   1.52 GB

EDIT3: when I tried it the second time, I got the rest of the error. 

Generating manifest manifest-qcow2.json
2024/09/12 00:06:18 error: cannot build manifest: failed inspect image: exit status 125, stderr:
time="2024-09-12T00:06:18Z" level=error msg="Refreshing container d0050cb416a5a5330081c076479d1c87a6492135226fe0cdbd2dfc7beff2fc53: acquiring lock 0 for container d0050cb416a5a5330081c076479d1c87a6492135226fe0cdbd2dfc7beff2fc53: file exists"
time="2024-09-12T00:06:18Z" level=error msg="Refreshing volume e41656ab0485b922450f80da38bf66c6e0e97e712bffb57c733592b778506032: acquiring lock 1 for volume e41656ab0485b922450f80da38bf66c6e0e97e712bffb57c733592b778506032: file exists"
time="2024-09-12T00:06:18Z" level=error msg="Refreshing volume 397d10b2974c8dcd2cf0dfb634cd463a4f2c084b6d1ac6fc1416ae281c5eccb3: acquiring lock 2 for volume 397d10b2974c8dcd2cf0dfb634cd463a4f2c084b6d1ac6fc1416ae281c5eccb3: file exists"
Error: localhost/bootcentos:latest: image not known
closet6 commented 2 months ago

I was creating the image as my account: podman build -t bootcentos but trying to search for it as root: sudo podman run ...

instead running: sudo podman build -t bootcentos

fixed it