Some times, good things that benefit everyone comes from the struggle of an individual.
I built the image knimer/erpnext to help me automate deployments. It helped @Clamsy deploy in a contained and special setup on a Synology box.
I notice a 6 Stars and more than 6,000 pulls.
Also, the image is frequently updated more than many other published images.
You can use the docker compose files used in the official docker repo. They offer a Main Compose file + Override Compose files that serve different purposes - Backup (Backup is not enabled by default), MariaDB, Traefik, No-proxy setup, Redis, Multi-bench…).
Also, add the overrides you want from the same repo under: Overrides/
Simply do:
Create the .env file with the needed vars in the compose file(s).
Modify the main compose file and any override compose files you need.
Run (this is an example, add needed override compose files as needed in your case…):
docker compose -f docker-compose.yml -f overrides/compose.noproxy.yaml up -d
I personally use these compose files and customize as needed.
Keep in mind that:
Your Custom App will be deleted when you update the image! As it is no longer there in the new containers running the new image.
You will need to manually install it again. Data loss is a high probability.
So, always use your custom image. Build it with your Custom Apps included. Which will give you the ability to update these Apps as needed, run before install and after install hooks to make sure data is kept.
Any other questions? let me know.
Also, provide as much details as you can. It will help to give a more relevant answer.
Agreed - Production image is all well but I would much rather have more control over where the data and config is stored etc. I’ve never had much luck with the custom image.