Closed adamzvolanek closed 3 months ago
Thanks for the PR! However, the files in the data
directory from the repo are present in the docker image (see line 43 of Dockerfile)
, so there's no need to also put them in the actual data directory that is mounted as a volume. You should be able to find these files in the running container at /app/data
, if that's not the case, this is a problem I should fix.
Thanks for the PR! However, the files in the
data
directory from the repo are present in the docker image (see line 43 ofDockerfile)
, so there's no need to also put them in the actual data directory that is mounted as a volume. You should be able to find these files in the running container at/app/data
, if that's not the case, this is a problem I should fix.
I went ahead and removed the appdata files:
Linux 6.1.99-Unraid.
root@dev-laptop:~# cd /mnt/user/appdata
root@dev-laptop:/mnt/user/appdata# ls
cloud/ core/ docs/ internal/
root@dev-laptop:/mnt/user/appdata# ls internal
jetlog/
root@dev-laptop:/mnt/user/appdata# rm -rf internal/jetlog
root@dev-laptop:/mnt/user/appdata# ls internal
However then fails out there after citing it cannot create the DB file. I can get the logs later because on mobile I cannot copy them fast enough.
Decided to spin up desktop. After the last line of the error, the container stops.
Yeah unfortunately this is due to an ownership error in the volume your provided. Have a look at #5 for more details
I am having issues with this as well. Trying to run this as a non-root user security context in kubernetes fails with the default command since gosu needs to be run as root. I don't like to allow containers to run with the root user if they don't need to.
If I set the security context user as nonroot, then gosu fails. If I set the security context user as root so gosu will work (again not my favorite), then the volume owner is set to root and I can't get the DB to create. I don't have other options that I know of.
I see that you opened and closed an issue about this problem (#30). Does this mean it's no longer a problem, or should I still look into this?
If the container cannot start as non-root, I see that as a problem. I'll open an issue about that so we can move this discussion there.
Adding some text and comments to the
readme.md
anddocker-compose.yaml
file. Namely about the need to populate the/data
directory with the items in the https://github.com/pbogre/jetlog/tree/main/data directory.