tholps.site
Tested on Debian Bookworm x64 & Ubuntu aarch64
Upon making a new knot instance the log is spammed with level=ERROR msg="failed to load db: unable to open database file: no such file or directory" and level=INFO msg="successfully finished setting up hooks" command=knot. The server directory is made but is empty
tholps.site
(author)
Also probably related: running ls -l in the host reveals the three created folders belong to root:root though the Dockerfile seems to set them to be owned by the created git user
I'm also running into this issue. I'm confused by what's happening with chown here cause like @tholps.site said, the Dockerfile is trying to set the owner to git:git, but in the host it says the owner is root:root - but when I try to chown it myself like @rad.being.cat's suggestion, it doesn't fix the problem for me. Not sure where to go from here.
Does PR #3 (merged) fix this? I'm not on Debian and these issues seem to only happen on Debian.
similar to @rad.being.cat, chown-ing the server/ directory in the knot's working directory on my host worked for me
Same on Arch
I'm unable to get this working with Podman, no matter how I configure the compose file or run the image directly. Quite stuck on this one (Fedora server, Podman)
Changed to docker and missed the issues with rootfs. Got it working now via docker at least.
tangled.org
totallynotseth.dev
rad.being.cat
singingpigs.online
knotbin.com
matts-corner.com
gov.glados.computer
gaiety.me
sachy.dev
julien.rbrt.fr