-
Notifications
You must be signed in to change notification settings - Fork 29
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
Is enableEmergencyMode = false
okay for digitalocean and vsphere where you have a console?
#287
Comments
Headless typically means when there is no GUI. This is a console terminal so it's fine. |
I am not too sure either whether this makes sense as a general default; I have "enableEmergencyMode = lib.mkForce true;" in my config. Maybe we should move it into the provider-specific modules? I.e. hetzner cloud has got a web console as well so emergency mode can be useful there. KVM consoles on dedicated hetzner machines might be more controversial, as those are attached manually by their support staff so one needs to wait between 15 and 120 minutes for console access. On the other hand: I personally don't remember an instance where emergencyMode would have been triggered but the machine was still able to boot far enough to be remotely accessible? Its most often faulty root disk or network configs for me. (I think this issues title is a bit misleading; it seems to be about the emergency console only @bbigras?) |
I initially created this issue because I can't seem to activate my nix-config using srvos on my digitalocean vps. Let me rename this issue and create a new one. |
enableEmergencyMode = false
okay for digitalocean and vsphere where you have a console?
DigitalOcean has a web console. Does it mean it's not headless?
srvos/nixos/server/default.nix
Lines 57 to 61 in d725309
The text was updated successfully, but these errors were encountered: