nix-installer icon indicating copy to clipboard operation
nix-installer copied to clipboard

Synology NAS is not supported: Action `create_group` errored

Open starsep opened this issue 2 years ago • 4 comments

On Synology NAS:

  • group can be added via synogroup --add nix
  • user can be added to group via synogroup --member nix $USER

starsep avatar Jul 20 '23 21:07 starsep

Thanks! Looks like we'll need to add support.

Hoverbear avatar Jul 21 '23 16:07 Hoverbear

Are you aware of any test VMs I might be able to use? Alternatively, what's the command to create a user? I only see how to add a user to a group.

Hoverbear avatar Sep 07 '23 16:09 Hoverbear

I am not aware of any Synology NAS VM.

User can be added using synouser {--add} username passwd full name expired email app privilege image image https://global.download.synology.com/download/Document/Software/DeveloperGuide/Firmware/DSM/All/enu/Synology_DiskStation_Administration_CLI_Guide.pdf

starsep avatar Sep 17 '23 21:09 starsep

Hello, I have a synology nas and wanted to install nix. I spent most of the day intending to try and create a PR adding support for synology to this installer. I was able to install nix, but patching the DetSys installer wasn't enough; some manual steps were required.

I've written detailed instructions in the readme on the main branch of my fork for anyone who wants to replicate.

Here's a summary of what I've learned:

  • Must set NIX_INSTALLER_EXTRA_CONF='filter-syscalls = false'
    • I hit the same issue as #324
  • The version of systemctl on the nas doesn't support the --now switch
    • I've got systemd 219 and it looks like the flag was added in v220.
  • The root partition doesn't have enough space to hold the nix store.
    • Following the advice of #695, I ended up creating a bind mount. I wasn't able to create an /etc/fstab entry. More on this in the next point
  • Synology's OS resets (at least some files in) /etc/ on reboot
    • This meant I couldn't edit /etc/fstab for my bind mount of the nix store
    • The only way I could get around this to make my mount persistent on reboots was to create an auto run script in the UI.
    • I also had to create a script to auto-start the nix daemon.

I've left my patches to the DetSys installer on the initial-pr branch of my fork, but I don't think it's worth opening a PR because of the manual steps needed. Thoughts?

adam-gaia avatar Aug 16 '24 23:08 adam-gaia