frappe
container-setup doesn't use built container?
02-build-setup builds a Docker image and tags as custom:15, however it doesn't say to set CUSTOM_IMAGE or CUSTOM_TAG in the env file, so the generated compose.custom.yaml file doesn't actually use it.
Absolutely right — the docs are misleading here. A PR to fix this would be very welcome!
I can update the docs; I just need to figure out how to get it working with a locally-built image. I couldn't get it working unless I pushed my custom image to Docker Hub, because it kept trying to pull the image even though it exists locally.
On November 10, 2025 1:54:06 AM PST, DanielRadlAMR @.***> wrote:
DanielRadlAMR left a comment (frappe/frappe_docker#1739)
Absolutely right — the docs are misleading here. A PR to fix this would be very welcome!
-- Reply to this email directly or view it on GitHub: https://github.com/frappe/frappe_docker/issues/1739#issuecomment-3510539927 You are receiving this because you authored the thread.
Message ID: @.***>
To create a final Compose file using your own image, you need to set the appropriate environment variables: Environment Variables env file setup
You should define the following variables with your image details:
-
CUSTOM_IMAGE— your custom image name -
CUSTOM_TAG— your image tag
Additionally, you may need to set the PULL_POLICY variable to a value other than always, since always will force Docker to pull a fresh image from a registry instead of using your locally built one.
See the Docker reference for more details:
docker compose pull_policy
@Daniel15 Yes you're right I have mentioned the issue in details here, the doc must be re-edited https://github.com/frappe/frappe_docker/issues/1742#issue-3616526887
