Open genevera opened 5 months ago
This is possibly related to the --dockerfile
flag... One work around is to let Docker build the original image, so you don't need to use the --dockerfile
flag. Another workaround is to try the --crt-api-version
global flag to specify the Docker API version to use there: slim --crt-api-version=1.25 build --dockerfile ./Dockerfile --tag image-name:slim --cbo-build-arg BUILD_ARG=arg --dockerfile-context $(pwd)
Unfortunately, using --crt-api-version=1.25
or --crt-api-version 1.25
results in the following error: time="2024-02-03T04:52:54-05:00" level=fatal msg="flag provided but not defined: -crt-api-version"
That last comment was all PEBKAC. I moved --crt-api-version before the verb and the error stopped.
I notice when trying to build from dockerfile that I get the following error no matter if i use --image-build-arch amd64
and/or --platform=$BUILDPLATFORM
in the dockerfile:
cmd=build info=build.error value='no matching manifest for linux/arm64/v8 in the manifest list entries' status='standard.image.build.error'
It does appear to work when using an extant image, however.
Want to confirm this behaviour
slimtoolkit version : 1.40.11 docker (client + engine) version: 24.0.7 OS: Arch Linux x64
Hey folks! Thanks for reporting! It'll likely be fixed in the next release by #641.
Expected Behavior
slim builds an image
Actual Behavior
I get an error about API versions, "cmd=build info=build.error status='standard.image.build.error' value='API /build requires version 1.25, requested version 1.24 is insufficient'"
Steps to Reproduce the Problem
1. run slim build --- Specifications ================= - Version: 1.40.11 - Platform: darwin/arm64