DrDaveD

A workaround is to do `unset DBUS_SESSION_BUS_ADDRESS` before doing `instance start`.

Perhaps if systemd is not available but `DBUS_SESSION_BUS_ADDRESS` is set it should just be a warning and not a fatal error.

The `--writable` option disables overlay and underlay, as discussed in this [doc section](https://apptainer.org/docs/user/latest/bind_paths_and_mounts.html#using-bind-or-mount-with-the-writable-flag). In order to be writable with a sif file, you must have a persistent overlay partition [embedded...

By the way, version 1.1.3 is quite old. I recommend upgrading to the latest release.

Since the fakeroot command is bind-mapped in from the host, it requires the container glibc library to be at least as new as the host's. This can be avoided by...

This is related to #1066, perhaps it is even a duplicate. Maybe with podman you need to bind in /etc/passwd or give some other option to have it define the...

Yes it does seem to be a regression. #1749 was supposed to have disabled the use of cgroups with `instance start --fakeroot`. I do not get an error in my...

Oh, my el9 error only happens when /etc/subuid is not set up. Jason, try it with `--ignore-subuid`. On el8 with `--ignore-subuid` I now get the original error reported in the...

The `faked` command ought to be bind mounted in whenever the fakeroot command is being used. I would next check with debug mode if it is attempting to do that...

I can reproduce the problem both in suid mode and user namespace mode on an al9 machine. Interestingly, I tested it first with a configuration that had `allow setuid-mount squashfs...