Support for Custom Dockerfiles using the Docker Executor

[kylejbrk]

Apologies if this is already supported but I didn't see it in the docs. Currently in the docs it says you can either supply an image name or existing container name to use with the docker executor: https://docs.dagu.cloud/features/executors/docker#configuration-reference-step-level

Notes:

• Set image, containerName, or both. If both are omitted, the step fails validation.
• With only containerName, the target container must already be running; Dagu will exec into it using the exec options.
• With both image and containerName, Dagu first attempts to exec into the named container. If it is missing or stopped, Dagu creates it using the supplied image (applying container/host/network settings) before running the command.

However I would like to use a local Dockerfile instead of using an official image or custom registry. Is it possible for me to point the Docker executor at a local dockerfile to use?

[yottahmd]

@kylejbrk You can config a step to execute command in a running container.

With only containerName, the target container must already be running; Dagu will exec into it using the exec options.

Regarding the following part:

However I would like to use a local Dockerfile instead of using an official image or custom registry. Is it possible for me to point the Docker executor at a local dockerfile to use?

It's not supported at the moment, but could be an interesting idea. I'll look into implementing this later.

[JohnMatthiasWabwire]

@kylejbrk Using the docker or nerdctl command line interface, the -file flag should be invoked with a my-custom-dockerfile.Dockerfile in the Root Directory. This allows the building of Custom Container Images alongside the Root Image.