ENOENT when trying to create a Unix domain socket under /tmp

[Patrik Wenger]

We use Snap to deliver CLI services, using strict confinement. On rare occasions when starting the service in production, we get an ENOENT error when the service tries to create a Unix Domain socket like `/tmp/xxx.ipc`. This error then persists until the machine is rebooted.

Could there be some kind of race-condition in snapd where the directory `/tmp/snap.my-service/tmp` (mapped to `/tmp` for the service) does not exist right away, and then somehow persists until the machine is rebooted?