Post #1848920
2026-04-28 08:41 UTC
Replies (1)
-
@smallsco@oldbytes.space 2026-04-28 16:50
@theirongiant@hachyderm.io @nikdoof@social.doofnet.uk Are you running netatalk in Docker? That's what I'm doing and it more or less just works 🤷♂️ You can see details of my afp.conf in this support ticket I created a while back: https://github.com/Netatalk/netatalk/issues/2747 My immediate thought is a permissions issue, given that you can see the host but not the volumes. If you want to allow guest access, you need to enable the uams_guest.so UAM in afp.conf. If you set “rwlist = username” where "username" is the name of your user, that will give you read/write access but make the volume read-only to guests. If you set "valid users = username" where "username" is the name of your user, that will give you read/write access but make the volume invisible to guests. And if you don't set either of those options then the volume will be readable and writable by guests. The other thing you need to do is set permission mappings, each of my volumes has the following configured in afp.conf: file perm = 0660 directory perm = 0770 Also paging the netatalk developer @dmark@hachyderm.io who is much better equipped that me to answer your question 🙂