Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to define/override entrypoint #79

Open
mickaelperrin opened this issue Feb 4, 2025 · 1 comment
Open

Add option to define/override entrypoint #79

mickaelperrin opened this issue Feb 4, 2025 · 1 comment

Comments

@mickaelperrin
Copy link

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.

@CybotTM
Copy link
Member

CybotTM commented Feb 5, 2025

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants