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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

runatlantis/atlantis:v0.18.4 fails to start #2201

Closed
jwtracy opened this issue Apr 14, 2022 · 4 comments
Closed

runatlantis/atlantis:v0.18.4 fails to start #2201

jwtracy opened this issue Apr 14, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@jwtracy
Copy link

jwtracy commented Apr 14, 2022

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Overview of the Issue

Running this image version results in failure on my Debian environment.

Reproduction Steps

> docker run runatlantis/atlantis:v0.18.4
standard_init_linux.go:219: exec user process caused: no such file or directory

Logs

standard_init_linux.go:219: exec user process caused: no such file or directory

Environment details

Config is irrelevant since the server won't start.

Additional Context

@jwtracy jwtracy added the bug Something isn't working label Apr 14, 2022
@andyshinn
Copy link

Usually this type of error can be an architecture mismatch (ie. arm64 vs amd64). What architecture is your Debian instance? A quick peek at https://hub.docker.com/r/runatlantis/atlantis/tags reveals there are only amd64 builds at the moment.

@jwtracy
Copy link
Author

jwtracy commented Apr 21, 2022

amd64 Runing 0.18.1 similarly does not result in this error and instead brings me to the CLI's usage help. I tried to dos2unix the files but didn't make any progress. Any luck reproducing this in a Debian environment?

@andyshinn
Copy link

Is this related? #2104

@jwtracy
Copy link
Author

jwtracy commented Apr 21, 2022

Yes, it seems to be the same issue. The release notes seem to document it well. 0.18.5 seems fixed as well. Thanks for the follow up. Unsure how I landed at 0.18.4 at the time of filing this issue.

@jwtracy jwtracy closed this as completed Apr 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants