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 create a Dockerfile that is based on the original one as the other comment suggests, or find the git repo of the original Image, fork it and add your changes to the Dockerfile.
If you want to include changes from the original one you'll need to set up some kind of regular job that checks for a new image or changes in the git repo and then applies your changes.
If you need it to be available at Dockerhub, ghcr or the like, you need some additional setup, usually a CI that pushes it.
thanks!
these aren't changes i can merge up, and i want to ensure it's always, ultimately, just pulling the original image with any new changes they make, and then making the changes i need, so i think the other solution is probably the most applicable for this problem.