-
Notifications
You must be signed in to change notification settings - Fork 231
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
nixos-infect on Ionos #188
Comments
Hi, working without any problem last day. first step : ssh-copy-id to root that's all, now do what you want with configuration.nix and let's nixos-rebuild switch do the job ( like hostname ;-) |
Hi Guillaume, thanks. Cheers. Richard |
Encountered the same issue with the Debian image from ionos. After reading @guiguid's comment, I installed the Ubuntu image through the cloud panel and followed the steps, which almost worked, except that I had to change one line of the script for it to run until the end: 376c376
< mv -v /boot /boot.bak || { cp -a /boot /boot.bak ; rm -rf /boot/* ; umount /boot ; }
---
> mv -v /boot /boot.bak || { cp -a /boot /boot.bak ; umount /boot/efi ; rm -rf /boot/* ; umount /boot ; } |
I finally made the effort to try again. Not sure, but part of my issue may have just been impatience (not waiting for the infect reboot), and not seeing the prompt change to nixos (so not recognizing that it worked). Hard to say, as much of my efforts were originally with a debian image, a year a go. Anyways, I install directly with the ubuntu 20.11 image, using #cloud-config. Caddy is available after the install, and I confirm the os with hostnamectl command. Eventually, I'll upgrade to a more expensive vps. Don't know if I can go directly to my sudo user.
|
Hi,
I struggled over getting nixos running on ionos vps. I tried nixos-infect, and loading an img with digital-ocean-init.nix too.
My main issue is I needed to rename the hostname. But I wanted to do this as part of the cloud-init. Eventually I got there (See below).
Not sure if the fqdn part is correct, or will cause problems with certain packages?
Or if the 127.0.0.2 is a possible issue as well?
The original hosts file had an 127.0.1.1 entry, that was causing a known bug. See. NixOS/nixpkgs#1248 (comment)
I have a $1.month Cloud Server S, CPU:1 vCore, RAM:0.5 GB, SSD:10 GB.
The DNS host name is *******.online-server.cloud
This is the /etc/hosts after infection
127.0.0.1 localhost
::1 localhost
127.0.0.2 *******.online-server.cloud *******
::1 *******.online-server.cloud *******
I reinstall the image as Debian 12. With root password, and ssh key. The cloud-init, is the same as the digital ocean example 2, with the extra four cc entries for the hostname and fqdn.
#cloud-config
preserve_hostname: false
prefer_fqdn_over_hostname: true
hostname: *******
fqdn: *****.online-server.cloud
write_files:
...
runcmd:
− curl https://raw.githubusercontent.com/elitak/nixos-infect/master/nixos-infect | PROVIDER=digitalocean NIXOS_IMPORT=./host.nix NIX_CHANNEL=nixos-22.11 bash 2>&1 | tee /tmp/infect.log
The text was updated successfully, but these errors were encountered: