Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

latest arm64 docker image fails to start #3867

Closed
adorn opened this issue Jan 20, 2025 · 5 comments · Fixed by #3868
Closed

latest arm64 docker image fails to start #3867

adorn opened this issue Jan 20, 2025 · 5 comments · Fixed by #3868

Comments

@adorn
Copy link

adorn commented Jan 20, 2025

Environment

  • Operating system: Mac M1. +Docker

docker pull --platform linux/arm64 postgrest/postgrest:latest
latest: Pulling from postgrest/postgrest
Digest: sha256:46519e461c7bbfdc49d6b5040f8ee2d379aceebe3a2f53743bc201fbe4fe5f46
Status: Downloaded newer image for postgrest/postgrest:latest
docker.io/postgrest/postgrest:latest

Description of issue

docker run --platform linux/arm64 --rm -it postgrest/postgrest:latest
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "postgrest": executable file not found in $PATH: unknown.

amd64-Image is working:

docker pull --platform linux/amd64 postgrest/postgrest:latest
latest: Pulling from postgrest/postgrest
Digest: sha256:46519e461c7bbfdc49d6b5040f8ee2d379aceebe3a2f53743bc201fbe4fe5f46
Status: Image is up to date for postgrest/postgrest:latest
docker.io/postgrest/postgrest:latest

docker run --platform linux/amd64 --rm -it postgrest/postgrest:latest
20/Jan/2025:15:47:45 +0000: Starting PostgREST 12.2.4...
20/Jan/2025:15:47:45 +0000: Listening on port 3000
....

@wolfgangwalther
Copy link
Member

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "postgrest": executable file not found in $PATH: unknown.

Urghs. We just changed the docker image creation process for the arm64 image, something must have been gone wrong.

Thanks for the report.

@wolfgangwalther
Copy link
Member

wolfgangwalther commented Jan 20, 2025

We most likely forgot to make postgrest actually executable (chmod +x). Thus, the file is there, but can't be run.

wolfgangwalther added a commit to wolfgangwalther/postgrest that referenced this issue Jan 20, 2025
This happened in 06aebfa and caused the arm64 docker image to not start
up properly.

Resolves PostgREST#3867
wolfgangwalther added a commit that referenced this issue Jan 20, 2025
This happened in 06aebfa and caused the arm64 docker image to not start
up properly.

Resolves #3867
wolfgangwalther added a commit that referenced this issue Jan 20, 2025
This happened in 06aebfa and caused the arm64 docker image to not start
up properly.

Resolves #3867
@wolfgangwalther
Copy link
Member

I removed the arm64 image from docker, so the v12.2.4 image is now single layer for amd64 only. Release is triggered and v12.2.5, which should hopefully fix this, is on it's way. The v12.2.5 and latest tags will then have the arm64 image again.

@wolfgangwalther
Copy link
Member

@adorn does it work better now?

@adorn
Copy link
Author

adorn commented Jan 21, 2025

Looks good:

➜  ~ docker run --platform linux/arm64 --rm -it postgrest/postgrest:latest
Unable to find image 'postgrest/postgrest:latest' locally
latest: Pulling from postgrest/postgrest
8bb55f067777: Pull complete 
a76afc99340e: Pull complete 
37eab0b5cf37: Pull complete 
d3e8dab0253f: Pull complete 
Digest: sha256:67c851793e115be6afba434bfd41908dfd155b868f0666ff11d6006be12c03ab
Status: Downloaded newer image for postgrest/postgrest:latest
21/Jan/2025:08:19:42 +0000: Starting PostgREST 12.2.5 (0bec15f)...
21/Jan/2025:08:19:42 +0000: Listening on port 3000
...

Thank you for your fast support!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants