Closed mil1i closed 7 months ago
Ok well, idk nvm. I tested on a separate macbook, and it worked. Came back to the original macbook, uninstalled finch
and deleted my ~/.finch
dir then reinstalled.
Now the builds are working.
We save container metadata in ~/.finch/.disks/<diskname>
, something in your container metadata must have been corrupted. Maybe due to a partial download?
Describe the bug Attempting to build a set of images, some work while others don't. Mostly testing with ubi9/openjdk images.
Specifically happening with
registry.access.redhat.com/ubi9/openjdk-11-runtime:latest
andregistry.access.redhat.com/ubi9/openjdk-11:latest
. The build fails on the firstRUN
command (I tried alterantive first RUN commands as well) with the below error:Exact same Dockerfile + commands builds with both
docker
andpodman
.This does NOT occur on other images though, such as the
ubi9/nodejs-16-minimal:latest
images. If I remove the--platform linux/amd64
from the build command it is successful, but need to ensure pulling a linux amd64 based image and not a darwin aarch64/arm.Steps to reproduce
Expected behavior Successful image build completion.
Screenshots or logs
vs docker (rancher/moby):