New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dockerutil.BuildEmptyImage() fails with bad API version #646
Comments
Interesting... need to investigate/repro. Either way, the next release should address this. Check back a bit later or follow me on Github or Twitter to be notified when the new release is out. |
Sounds good, thanks. I'll see how the next version works out. We're still having some build issues, but it looks like if we set a |
For reference, other versions may work (
in our pipeline |
@jimcottrell this might work as-is https://github.com/mintoolkit/mint/releases/tag/1.41.1 let me know if you still have problems there |
I've tried with v1.41.1 and no explicit |
@jimcottrell which version of Docker do you have installed? Are you on Mac or Linux? If you are on Linux are you using Docker Desktop or only Docker Engine? If you are on a Mac is it an AMD or an M1/M2? Trying to repro... more info on your environment will help |
Getting this on Fedora 39 with the latest stable docker-ce and slim installed.
Setting Seems to be a common problem looking at #637 and caused by #641 |
@sammcj Here's the Vagrant-based repro with Fedora 39 and Docker 26.1.1. You should be good with the release version in the repro config. The release version you shared in this issue is out of date. |
I've got a CI/CD pipeline that's run occasionally when we rebuild a image and create an optimized version with Slim. Without anything having changed that I'm aware of (same Slim version, same pipeline runner), this process has started failing with:
I thought this might be related to #637, but it seems to be a separate issue, and the same thing happens whether or not I try setting
--crt-api-version
. Having updated everything to the latest versions, the problem continues. The issue seems to be specific to this environment, as a local build works.Steps to Reproduce the Problem
(trivial reproduction; of course not our actual image)
Specifications
slim version
:The text was updated successfully, but these errors were encountered: