-
-
Notifications
You must be signed in to change notification settings - Fork 151
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
Missing archs for images on dockerhub (Probably pipeline issue). Since 0.5.3-alpha.7 #116
Comments
pascaldornfeld
changed the title
Error when launching container different than tag 'master'
Missing archs for containers on dockerhub (Probably pipeline issue)
Nov 9, 2021
pascaldornfeld
changed the title
Missing archs for containers on dockerhub (Probably pipeline issue)
Missing archs for images on dockerhub (Probably pipeline issue)
Nov 9, 2021
pascaldornfeld
changed the title
Missing archs for images on dockerhub (Probably pipeline issue)
Missing archs for images on dockerhub (Probably pipeline issue). Since 0.5.3-alpha.7
Nov 9, 2021
It seems that the GitHub action I have when it gets to building arm64, it seems to delete amd64 images (??) |
Closing in favour of #142 |
github-project-automation
bot
moved this from Low Priority Backlog
to Done
in Revolt Project
Jan 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When launching the self-hosted docker-compose I am getting errors with the api/server part.
api_1 | standard_init_linux.go:219: exec user process caused: exec format error
I am getting the same with revoltchat/server:latest, 0.5.3-alpha.8 and 0.5.3-alpha.7 but revoltchat/server:master works fine. I didn't try older tags.
I found out that the error is usually connected to a wrong image arch. My system is amd64.
$ uname -a
Linux debian-server 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux
After checking dockerhub I found out that master has only amd64 arch while the other have arm64.
See this:
The text was updated successfully, but these errors were encountered: