-
Notifications
You must be signed in to change notification settings - Fork 312
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
Starting a Myst connection in Docker crashes host OS (Ubuntu, Alpine and Amazon Linux 2) #6063
Comments
IDEALLY there would be NO NEED for |
Oh I noticed these OSes aren't officially supported, so I spun it up in Ubuntu 22, which is officially supported. Same thing. |
This is where it dies:
Apparently, it keeps going after I can no longer interact with the server:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I run the default
docker run
from the README:I shell into the container, register and top up.
Then, I run
myst connection up
and I can't reach the server anymore until I reboot it.Same thing on Ubuntu 24, Alpine and AL2. Running on EC2.
This doesn't happen if I remove
--net host
but then ofc p2p doesn't properly work. I'm guessing a faulty iptables rule.The text was updated successfully, but these errors were encountered: