If you’d done a docker commit on your earlier changes, they’d have stuck as well.

The proper way to do this is to fork their image project and alter the nginx files that get incorporated in the build. Then you can run the stack with a build command instead of an image reference, and git pull your fork whenever there’s upstream merges. Or Action the fork to build an image for you every time it gets merged that you reference in your docker compose instead.

deleted by creator

This might be the last chance to migrate from Gitea to Forgejo and avoid whatever trainwreck Gitea is heading for. It’s going to a hardfork soon.

I’ve used Joplin for years. IDK why people have a hate on for it, it’s fine.

I guess on the rare occasions you need to specify the driver, this is the answer. Otherwise, it’s a lot of extra work for no real benefit.

I like having everything to do with a container in one folder, so I use ./ the bind mounts. Then I don’t have to go hunting all over hells half acre for the various mounts that docker makes. If I backup/restore a folder, I know I have everything to do with that stack right there.

This is exactly why you don’t use anything from Oracle, especially free stuff like OCP. If you think you’re not going to regret it eventually, you’re fucking wrong.

That sounds like a “sell it and make it someone else’s problem” situation.