-
Notifications
You must be signed in to change notification settings - Fork 28
NixOS container not starting in NixOS host #22
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
Comments
I had no idea what's going on when you first reported it, but now I've confirmed it to be an AppArmor issue. It doesn't report anything to kernel log which had me confused. We'll get it sorted next week or so. |
Should be fixed by 23ac899, which was deployed to staging yesterday. systemd-nspawn --private-network and thus nixos containers should now work. Can you confirm? |
Confirming the container is up. Got a couple of networking problems but that could just be bad config. This issue can be closed as far as I'm concerned. Thanks! |
ok, maybe not:
There seems to be some kind of a problem with networking. I'll dig deeper. |
I don't see any showstopper in the log you sent. The device related errors should be harmless. Here's what I tried:
Imperative containers with network as in https://nixos.org/nixos/manual/index.html#sec-container-networking work for me too, even the NAT setup described below. My guess is that you hit firewall in the container and you need to open ports, that was my only issue. If you still have problems, send us your configuration and show what do you expect to be working and doesn't. |
I got carried away by the
You're right, there's no problem, I just forgot that declarative containers don't get their network configured automatically. |
Great to hear that, closing. |
NixOS guest container created on a NixOS Host running in vpsadminos is not starting.
Container snippet
Host snippet
Result:
Journal:
The text was updated successfully, but these errors were encountered: