From 8771e02c400140fd43151d38a987662d7a71f022 Mon Sep 17 00:00:00 2001 From: redbeardymcgee Date: Fri, 8 Nov 2024 22:17:42 -0600 Subject: [PATCH] fix weechat persistence This is still a hack. Something is wrong with permissions upstream. They document 777 as the solution but that should never be a solution. I think I want to explore the container build, especially since the permissions error is reported on github issues #10. They provided an unrelated fix to UID inside the container, but it didn't help about 777. --- quadlets/weechat.container | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/quadlets/weechat.container b/quadlets/weechat.container index ade88dd..c7d69fb 100644 --- a/quadlets/weechat.container +++ b/quadlets/weechat.container @@ -15,8 +15,7 @@ HostName=weechat AutoUpdate=registry # Persist the full home dir -# FIXME: weechat throws tons of permission errors. Could be related to me -# destroying and rebuilding the volumes and disks and $ctuser on my end +# FIXME: requires `chmod 777 /volumes/books/weechat/home/user` on host Volume=/volumes/books/weechat/home/user:/home/user # FIXME: Better way to attach stdin and tty