Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing to start up container, exec format error #988

Closed
2 of 13 tasks
rgallo opened this issue Apr 4, 2023 · 5 comments
Closed
2 of 13 tasks

Failing to start up container, exec format error #988

rgallo opened this issue Apr 4, 2023 · 5 comments

Comments

@rgallo
Copy link

rgallo commented Apr 4, 2023

馃悰 Bug Report

After updating this morning on the release branch, I'm getting this error and my container is shutting down:

standard_init_linux.go:230: exec user process caused: exec format error

I have Watchtower set to update this container automatically, the last time before today it was updated was February 18th.

馃敩 How To Reproduce

Steps to reproduce the behavior:

  1. Start docker container

Code sample

Environment

Where are you running/using Password Pusher?

  • pwpush.com
  • Docker
    • pwpush-ephemeral
    • pwpush-mysql
    • pwpush-postgres
    • custom image
  • Heroku
  • Digital Ocean
  • Microsoft Azure
  • Google Cloud
  • AWS
  • Source Code
  • Other (please specify)

If applicable, what version of Password Pusher?

pglombardo/pwpush-ephemeral:release

Screenshots

馃搱 Expected behavior

馃搸 Additional context

@github-actions
Copy link

github-actions bot commented Apr 4, 2023

Hello @rgallo, thanks for contributing to the Password Pusher community! We will respond as soon as possible.

@pglombardo
Copy link
Owner

pglombardo commented Apr 4, 2023

Hi @rgallo - which container tag and arch are you using? arm or amd?

Cancel that - I saw that you pointed out release. How about arch?

Tested locally and can't reproduce so far.

@pglombardo
Copy link
Owner

I got it - fix incoming.

@pglombardo
Copy link
Owner

Docker has an issue with tagging multi-arch builds (it doesn't support it). The wrong arch was pushed to the release tag. It should be fixed now. Could you confirm?

@rgallo
Copy link
Author

rgallo commented Apr 5, 2023

Looks good now, thanks!

@rgallo rgallo closed this as completed Apr 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants