You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
STEP 1/2: FROM quay.io/libpod/testimage:20240123
STEP 2/2: RUN echo hi from 1
Error: checking if cached image exists from a previous build: getting top layer info: layer not known
or
STEP 1/2: FROM quay.io/libpod/testimage:20240123
STEP 2/2: RUN echo hi from 1
hi from 1
COMMIT c1
Error: committing container for step {Env:[PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin] Command:run Args:[echo hi from 1] Flags:[] Attrs:map[] Message:RUN echo hi from 1 Heredocs:[] Original:RUN echo hi from 1}: copying layers and metadata for container "a8d0253ccd5f337ca69e106657dc645e4926b20d9775621827b6ec118bcb35fa": committing the finished image: creating image "41778f8cf15b69d1fdb79d5bb744ba65eac877e27a21dd12af8700594d88585b": layer not known
The rmi seems important; I can't get it to fail (at least not within my patience tolerance of ~10m) if I omit rmi from either loop.
Testing with podman fails MUCH faster than buildah, for reasons I don't understand, and also fails sometimes in window 2. Buildah only fails in window 1.
This is blocking parallelization of podman test 070-build and I bet this is one of the uncategorized weirdnesses I've seen in #5552 but didn't follow up on.
The text was updated successfully, but these errors were encountered:
This is two builds with --layers=true, which means they're reading each other's work as cache candidates, which is not something #5686 was concerned with.
Need --layers=false in podman build, otherwise a buildah race
can trigger "layer not known" failures:
containers/buildah#5674
Signed-off-by: Ed Santiago <[email protected]>
This might be the same as containers/podman#23331 . If it is, someone please close this or move.
Setup:
$ for i in 1 2;do printf "FROM quay.io/libpod/testimage:20240123\nRUN echo hi from $i\n" >Containerfile$i;done
In window 1:
$ while :;do buildah build -t c1 --layers=true -f Containerfile1 || break;buildah rmi c1;done
In window 2:
$ while :;do buildah build --layers=false -t c2 -f Containerfile2|| break;buildah rmi c2;done
Within 30-60s, window 1 will barf:
or
The
rmi
seems important; I can't get it to fail (at least not within my patience tolerance of ~10m) if I omitrmi
from either loop.Testing with
podman
fails MUCH faster than buildah, for reasons I don't understand, and also fails sometimes in window 2. Buildah only fails in window 1.This is blocking parallelization of podman test
070-build
and I bet this is one of the uncategorized weirdnesses I've seen in #5552 but didn't follow up on.The text was updated successfully, but these errors were encountered: