mnutt has quit [Remote host closed the connection]
mnutt has joined #sandstorm
mnutt has quit [Remote host closed the connection]
mnutt has joined #sandstorm
mnutt has quit [Read error: Connection reset by peer]
mnutt has joined #sandstorm
mnutt has quit [Ping timeout: 256 seconds]
mnutt has joined #sandstorm
mnutt has quit [Remote host closed the connection]
mnutt has joined #sandstorm
mnutt has quit [Remote host closed the connection]
torhex-pasmul[m] has joined #sandstorm
<torhex-pasmul[m]>
hi. I'm working on running Sandstorm on NixOS and it's been an interesting challenge.
<torhex-pasmul[m]>
So far I've gotten to build and start but it's failing with this in the logs: sandstorm/run-bundle.c++:1455: failed: mount("proc", "proc", "proc", MS_NOSUID | MS_NODEV | MS_NOEXEC, ""): No such file or directory
<ocdtrekkie>
There are definitely a few people interested in that. garrison was working on it last year I think.
<torhex-pasmul[m]>
Yes, I started from his work.
<isd>
Were you the one who opened that PR?
<torhex-pasmul[m]>
Yes.
<torhex-pasmul[m]>
Anyway, I'm not familiar enough with user namespace stuff to figure this one out. As far as I can tell I've got user namespace support enabled, but nobody seems to have an explanation for ENOENT from trying to mount proc
<isd>
I'm not sure what that would be either
<isd>
If you're just looking to use sandstorm in the short term, it might not be a bad idea to punt on building it with nix and just use the usual process (either using the binaries we distribute, or building from source without nix -- if you hit issues with the latter I definitely want to know about them). If you want to slog through it with nix it would be a good contribution, but there's a reason that repo is WIP.
<torhex-pasmul[m]>
OK. Well, building works (or at least doesn't produce errors). So yeah the next step would be to just try the install script and compare behavior.
mnutt has joined #sandstorm
<torhex-pasmul[m]>
Tried the install script. It produces a setup in `/opt/sandstorm` that starts successfully. Obviously it can't write to `/etc/systemd` or `/usr/local/bin` but the bits before that seem to do ok.
xet7 has joined #sandstorm
<isd>
Ok, so something must be off with the build then.
<torhex-pasmul[m]>
Hmm.
<torhex-pasmul[m]>
Trying my custom build succeeds with the proc mount and then dies on something mongo related.
<isd>
Do you have an error message handy?
<torhex-pasmul[m]>
aah, the bundled `bin/mongo` didn't get patchelf'd
<torhex-pasmul[m]>
easy enough to fix.
<torhex-pasmul[m]>
Wondering about the mount thing still, I wonder if it just doesn't work outside of `/opt/sandstorm`