docker installs need a `chown` for `files/`

a bunch of people have reported recently that a newly-started docker sharkey can't write to files/ until it's chown-ed to 991

that should either not be necessary, or be documented better (we only have that bit in the "upgrade" notes)

this could be caused by any of:

• not running as root (we're not going back to running as root!)
• changing the way the directory is created by sharkey (unlikley, but we did change it)
• changing the way the directory is created inside the container
• something else?

added tooling label

Do you mean chmod to 663? That worked for me!

no, I mean chown so that the directory is owned by the user id 991 (and group id 991)

0663 as a set of permissions is subtly wrong: it means owning user and group can read and write (but not cd into the directory), and that everyone else can write and cd into it.

please chown -R 991:991 files/ && chmod 755 files/ to fix your directory

(yes, I had written the wrong user id in the issue description, apologies)

changed the description

@transitory @tess I feel you may be able to help with this

huuuuuuuuuuh

https://activitypub.software/TransFem-org/Sharkey/-/blob/develop/Dockerfile?ref_type=heads#L44

&& chown sharkey:sharkey /sharkey/files \

are they mounting it as a volume maybe?

I guess so

because that directory contains all the drive files, so its contents must survive after the container gets shut down

AIUI, a chown inside the Dockerfile affects the filesystem inside the container image, and does nothing to the filesystem in the host (ok, unless it's in a CMD or something like that).

probably related: people reported a very similar problem upstream a long time ago https://github.com/misskey-dev/misskey/issues/9564