You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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?
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.
Community Note
Overview of the Issue
Running this image version results in failure on my Debian environment.
Reproduction Steps
Logs
Environment details
Config is irrelevant since the server won't start.
Additional Context
The text was updated successfully, but these errors were encountered: