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

Container crashed due to invalid instruction in argon2.so, under Haswell or older #862

Closed
nroach44 opened this issue Oct 26, 2023 · 6 comments
Assignees
Milestone

Comments

@nroach44
Copy link

nroach44 commented Oct 26, 2023

Describe the bug
When attempting to run this container on a machine with an Ivy Bridge / Haswell CPU, the container will start up, but when "logging in" to create a password, the container dies.

The following is seen in syslog:

Oct 26 09:57:55 uranus kernel: traps: perl[144999] trap invalid opcode ip:7f626e209811 sp:7ffedc4b5b10 error:0 in Argon2.so[7f626e206000+5000]

Since that file seems to live at /diff/app/local/lib/perl5/x86_64-linux-thread-multi/auto/Crypt/Argon2/Argon2.so in the container's work dir, I'm logging it here. If it should be filed against the main container let me know.

Since Haswell and Ivy Bridge are old, but still quite capable for self hosting, and there's no mention of required CPU functions for x86_64 on the Alpine Linux wiki, I believe this to be a bug.

To Reproduce
Run the container on a machine with an Ivy Bridge or Haswell CPU.

Expected behavior
Container runs without issue.

Screenshots
Nil

Environment:
Debian 12, podman.

@nroach44 nroach44 added the bug label Oct 26, 2023
@stigtsp
Copy link
Contributor

stigtsp commented Oct 26, 2023

Maybe relevant upstream issue:

@stigtsp
Copy link
Contributor

stigtsp commented Oct 26, 2023

Hi @nroach44

This is likely caused by the issue linked above, where Crypt::Argon2 is built using -march=native. I hope this will be fixed soon. In the meanwhile, you can try to rebuild the docker container on your machine - it should work.

@jhthorsen
Copy link
Collaborator

@nroach44, @trymbill, @jberger: If you have some time to spare, could you test v8.06?

@nroach44
Copy link
Author

#worksForMe

Both in general and when changing my password to a temp password, logging out and back in, and then changing it again.

@jberger
Copy link
Collaborator

jberger commented Mar 20, 2024

I'm not having luck with v8.06. Still cannot login, the pod crashes when attempting. I will also note however that the help page displays v8.05 even when I've deployed v8.06. Is there an easy way to confirm which code I'm running?

@jhthorsen jhthorsen self-assigned this Mar 20, 2024
@jhthorsen
Copy link
Collaborator

I'm going to close this issue, since it seems resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants