You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The classic containers work perfectly fine when running them as an unprivileged user (user: nobody:nobody or similar in the compose file).
However, in the s6 container this does not work out of the box, making /data a volume pointing to a directory owned and writable by that particular user fixes it, but the chown root:root ... calls for the secrets still fail (not a problem though).
It would be nice if those commands were skipped when not running as root.
I think it would make sense in any case to default to NOT running hbbs/hbbr as root, since they do not seem to need such privileges.
The text was updated successfully, but these errors were encountered:
The classic containers work perfectly fine when running them as an unprivileged user (
user: nobody:nobody
or similar in the compose file).However, in the s6 container this does not work out of the box, making
/data
a volume pointing to a directory owned and writable by that particular user fixes it, but thechown root:root ...
calls for the secrets still fail (not a problem though).It would be nice if those commands were skipped when not running as root.
I think it would make sense in any case to default to NOT running hbbs/hbbr as root, since they do not seem to need such privileges.
The text was updated successfully, but these errors were encountered: