Open jaredledvina opened 2 years ago
I have the same problem in docker
Same for me:
standard_init_linux.go:228: exec user process caused: exec format error
Updating my containers this morning seems to have fixed the problem.
I suspect there's a race in the master container build process where the wrong arch got pushed and tagged as amd64. I'm not familiar with multi-arch images though. I'm also not sure if this can easily happen on any commit to master or not.
Type: Bug Report
Your Environment
Summary
I'm attempting to run the latest master of the docker container as I typically do, it seems like there might be an Arch issue?
This isn't an issue with the one tagged latest:
However, is similar if you force the wrong arch:
Interestingly, this is not an issue with the
master-distroless
image:Expected Behavior
The latest master image would run like it has for a while now and how the current latest image runs.
Current Behavior
Master image fails due to exec issue.
Possible Solution
I suspect the build on master pushed a different arch to the 'master' tag than the typical
amd64
. Perhaps we need to add support for each arch on master?Steps to Reproduce
podman run docker.io/jesec/flood:master
Context
Trying to run flood in a normal podman install and it's failing. It's been a while since I've pulled the image though, so I'm not sure which change caused this.