@alexmurray we have followed up on this and it got us a bit further, but now we have an issue where the code we are snapping calls setegid and throws a chain of errors for us.
Trying to execute the
srun command in our snap I get the following:
$ slurm.srun -pdebug -n1 -l hostname -vvvvvv
srun: error: task 0 launch failed: Slurmd could not set UID or GID
Looking in the slurm logs I see:
[2020-05-06T03:55:39.809] [2.0] error: setegid: Operation not permitted
Snappy debug shows:
= Seccomp =
Time: May 6 03:33:30
Log: auid=4294967295 uid=0 gid=0 ses=4294967295 pid=4452 comm="slurmstepd" exe="/snap/slurm/x1/sbin/slurmstepd" sig=0 arch=c000003e 119(setresgid) compat=0 ip=0x7fd2d6d5bd9d code=0x50000
* adjust program to not use 'setresgid' until per-snap user/groups are supported (https://launchpad.net/bugs/1446748)
Looking further into the same
mgr.c I see this which leads me to believe that executing as the
snap_daemon user might be a way around this. Am I on the right track here in thinking that running the process as the
snap_daemon user could be a path forward?
Do you have advice on how might be able to get through this?