-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Docker run leads to error #2
Comments
Are you possibly on the arm32 architecture? I think there is also a playbook bug, in the sense that self-building is not automatically enabled for you when it should be. |
I'm using amd64 (x86_64). |
The image should be multi-arch and support both amd64 and arm64. Could you try pulling it again? |
It seems like the image is not built - when i do it by hand it seems to work but when I use the docker run command I've shown in my first comment I still receive |
I was able to surpass the problems by building the image locally and then use it in my matrix setup. That works, at least it compiles and starts but during the usage of the bot I now receive these errors:
Could it be an issue with the docker networks? |
You're right - the I have rebuilt it and it seems to be fine now. I'll keep an eye on future CI runs and see if it can be reproduced. The error that you're quoting seems to indicate a that the bot cannot connect to the Matrix server. If you're using the Ansible playbook with the default Traefik reverse-proxy server, it should be communicating with Synapse via If you're using another reverse-proxy, you may need to adjust the configuration and/or container networks. About self-building not kicking in correctly on Self-building is correctly enabled for architectures other than |
Related to #2 We've had a few more instances of the same issue since then.
I currently try to get the bot running in my Matrix Ansible deployment but when In try to run the docker container I receive this error:
/bin/sh: 1: /app/baibot: Exec format error
I user Ubuntu 24.04.1 LTS and Docker version 27.2.0, build 3ab4256
this is the command I try to execute:
The text was updated successfully, but these errors were encountered: