Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Either this means you won't get future updates, or future updates will still overwrite your change. The proper way to do this would be to mount your own config over the one in the container, though this may have negative effects if the container config changes in the future. You might be able to mount /dev/null over the log file if you don't care about the logs at all.
I don't believe there's any way to specify modifications to someone else's containers without making your own image, unfortunately.
So an issue i had was that I'd try to mount folders to this image but they wouldn't show up, but when I tried mounting it to a different image, it did. I'm not sure what I did wrong here, but I worked at it for a while and I'm still new to TruNas. But at least with this image, I don't mind too much about updates and it's an easy change that I can do again. Thanks for the feedback though, I'll be keeping this in mind and try to do things in a more "correct" manner 🙂
This is not a truenas issue - its a docker thing. You’d do better by making your own docker-file and do your customisation the docker way.