Open mstewart14 opened 6 months ago
What do the container logs say?
Mine say this:
standard_init_linux.go:178: exec user process caused "exec format error"
standard_init_linux.go:178: exec user process caused "exec format error"
standard_init_linux.go:178: exec user process caused "exec format error"
standard_init_linux.go:178: exec user process caused "exec format error"
This indicates an architecture conflict, and it appears to be the case. The DockerHub image says:
$ docker inspect bf07f8de4f4a | grep Arch
"Architecture": "arm64",
... and I'm trying to run it on:
$ docker info | grep Arch
Architecture: x86_64
This image needs to be built for multiple architectures - I'll try a manual build first, then will see if it can be PR'd.
tried the following (note, I'm running on amd64 so had to build it myself) tried the following as a docker-compose.yml
services: receipt-parser-server: image: 76b8a403068d #had to build locally for amd64 container_name: receipt-parser environment:
instantly starts restarting and never comes up all the way. why is that? running the launcher script (correctly modified to refer to this image and the IP) works and I end up with a running container. It's important for me for back-up and management purposes.
any help or clues would be appreciated