You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we can override the default command of a docker image by using the label "ofelia.job-run.TAG.command", it would be great if we could also define/redefine/delete the entrypoint by having a "ofelia.job-run.TAG.entrypoint" label.
Use case I encounter, is that I reuse the same image as the database image in a job-run. That image contains the backup script I want to trigger, but the entrypoint does some things that I don't need, and I would like to bypass.
When using the CLI the argument to pass to a docker run command is simply: --entrypoint="". So i guess that an empty label will do the thing for me and will allow also to redefine the entrypoint if needed by others.
The text was updated successfully, but these errors were encountered:
Just to mention it: DBMS should be run alone in a container without any additions - not even scripts. Any maintenance, backup or whatever scripts should be delivered and run in it's own container image - and required access to the database should be done via internal network or shared volume(s).
Hi,
Currently, we can override the default command of a docker image by using the label
"ofelia.job-run.TAG.command"
, it would be great if we could also define/redefine/delete the entrypoint by having a "ofelia.job-run.TAG.entrypoint"
label.Use case I encounter, is that I reuse the same image as the database image in a job-run. That image contains the backup script I want to trigger, but the entrypoint does some things that I don't need, and I would like to bypass.
When using the CLI the argument to pass to a docker run command is simply:
--entrypoint=""
. So i guess that an empty label will do the thing for me and will allow also to redefine the entrypoint if needed by others.The text was updated successfully, but these errors were encountered: