Feature Request: Ability to Change Docker Command

[nahtnam]

I would love to be able to set a custom command when deploying a docker image

Current workaround: Create a docker-compose deployment with one service with the custom command

[AlejandroAkbal]

I think it's now available, if so, please close this conversation

[nahtnam]

I don't think so? I only see these options: https://coolify.io/docs/custom-docker-options

[andrasbacsai]

why do you want to change it? can you please give me an example use-case?

[nahtnam]

For example, glitchtip requires a webserver and worker. Because custom commands for docker files are not supported, I have to run it like this:

FROM glitchtip/glitchtip:latest

CMD ./bin/run-celery-with-beat.sh

Not the biggest deal but it is common to have to do this sometimes. It is also possible to do via docker compose, but I prefer to have a different resource for each running task instead of docker compose

[jsmits]

I have a similar use-case, also with a worker using the same image, but the worker is started with a different command.

[nahtnam]

Another use case would be starting the docker container using https://infisical.com/

[shintaii]

Why i would like to change it? Because i do not want to build a seperate docker image, for an application, that only has 1 different argument in the startup.

So for example i have a container, running an app, that runs in multiple modes.
In the entrypoint you can make it so that it exec's all commands passed to the start. I.e.:

docker run IMAGE queue1
docker run IMAGE queue2
docker run IMAGE queue2 --debug

[branch14]

👍 I want that feature to run savonet/liquidsoap, which is build in a way that it takes the script to run as an argument.

Being able to overwrite the entrypoint via custom docker options would be workaround though.

[markitosgv]

same here, workers and web on same image, so I need to use different CMD