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?

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

[ThomasAunvik]

@andrasbacsai another case, default for example in for keycloak, they use run arguments to set the runtime.

https://www.keycloak.org/server/containers#_starting_the_optimized_keycloak_container_image

podman|docker run --name mykeycloak -p 8443:8443 -p 9000:9000 \
        -e KC_BOOTSTRAP_ADMIN_USERNAME=admin -e KC_BOOTSTRAP_ADMIN_PASSWORD=change_me \
        mykeycloak \
        start --optimized --hostname=localhost

And here is how the Dockerfile would look:

https://www.keycloak.org/server/containers#_writing_your_optimized_keycloak_containerfile

FROM quay.io/keycloak/keycloak:latest as builder

# Enable health and metrics support
ENV KC_HEALTH_ENABLED=true
ENV KC_METRICS_ENABLED=true

# Configure a database vendor
ENV KC_DB=postgres

WORKDIR /opt/keycloak
# for demonstration purposes only, please make sure to use proper certificates in production instead
RUN keytool -genkeypair -storepass password -storetype PKCS12 -keyalg RSA -keysize 2048 -dname "CN=server" -alias server -ext "SAN:c=DNS:localhost,IP:127.0.0.1" -keystore conf/server.keystore
RUN /opt/keycloak/bin/kc.sh build

FROM quay.io/keycloak/keycloak:latest
COPY --from=builder /opt/keycloak/ /opt/keycloak/

# change these values to point to a running postgres instance
ENV KC_DB=postgres
ENV KC_DB_URL=<DBURL>
ENV KC_DB_USERNAME=<DBUSERNAME>
ENV KC_DB_PASSWORD=<DBPASSWORD>
ENV KC_HOSTNAME=localhost
ENTRYPOINT ["/opt/keycloak/bin/kc.sh"]

[markitosgv]

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

[KMarshland]

One other workaround I've found is using environment variables to change the CMD dynamically. For my case (a rust app with a server and a worker), I have the CMD set to:

CMD ./target/release/${BINARY_NAME:-server}

For the worker, I can set the BINARY_NAME environment variable to worker

[danielehrhardt]

Cannot add APP_Origin and API_HOST: https://docs.growthbook.io/self-host/env#domains-and-ports

[zastrixarundell]

An example of such an application would be a rails application. You start the server with bundle exec rails s but you can also start async job processing by running bundle exec sidekiq.

I have never seen a custom Dockerfile for sidekiq.

My company uses EasyPanel which has the option to change the docker command:

On my personal projects I have an app which can work either as a webcrawler and/or a server (I know that it should've been seperate but oh well). I can specify via an argument whether it should works with the server or not.

[theDanielJLewis]

Any solution for this, yet?

In my case, I'm having trouble trying to make MongoDB work as a shard config server. It seems I have to explicitly add the --configsvr argument to the mongod command, but I don't see any way to do that inside Coolify. It seems like the only option would be to switch to a custom Docker image or compose setup, but then that gets much more complicated and misses a lot of Coolify's features.

[theDanielJLewis]

Aside: the problem I'm running into is more of a Docker problem, because the Mongo Docker image isn't working properly when env username and password are passed. Nonetheless, the workaround (until the Docker image is fixed) is to replace the command, which Coolify doesn't support.

[zastrixarundell]

Afaik, the simplest way to do this for custom containers is to setup a custom entrypoint which is a bash script and set the default variable as the default execute command.

Something like this:

coolify-fix.sh:

#!/bin/bash

/bin/bash -c "${DEPLOY_COMMAND:-mix phx.server}

End of Dockerfile:

ENTRYPOINT [ "./coolify-fix.sh" ]

I was then able to run the following commands:

$ docker build . -t my_app
$ docker run -e DEPLOY_COMMAND="echo 'hello there'" my_app
hello there

Of course, this is a workaround and coolify REALLY needs the ability to change the command. This works on an app I made, sure, but won't work if I were to pull an image of another app of which I'm not the maintainer of.

[twilwa]

This is currently the situation i'm in -- my dockerfile looks like the following:

# Use a specific Node.js version for better reproducibility
FROM node:23.3.0-slim AS builder

# Install pnpm globally and necessary build tools
RUN npm install -g [email protected] && \
    apt-get update && \
    apt-get upgrade -y && \
    apt-get install -y \
        git \
        python3 \
        python3-pip \
        curl \
        node-gyp \
        ffmpeg \
        libtool-bin \
        autoconf \
        automake \
        libopus-dev \
        make \
        g++ \
        build-essential \
        libcairo2-dev \
        libjpeg-dev \
        libpango1.0-dev \
        libgif-dev \
        openssl \
        libssl-dev && \
    apt-get clean && \
    rm -rf /var/lib/apt/lists/*

# Set Python 3 as the default python
RUN ln -sf /usr/bin/python3 /usr/bin/python

# Set the working directory
WORKDIR /app

# Copy application code
COPY . .

# Install dependencies
RUN pnpm install --no-frozen-lockfile

# Build the project
RUN pnpm run build && pnpm prune --prod

# Final runtime image
FROM node:23.3.0-slim

# Install runtime dependencies
RUN npm install -g [email protected] && \
    apt-get update && \
    apt-get install -y \
        git \
        python3 \
        ffmpeg && \
    apt-get clean && \
    rm -rf /var/lib/apt/lists/*

# Set the working directory
WORKDIR /app

# Copy built artifacts and production dependencies from the builder stage
COPY --from=builder /app/package.json ./
COPY --from=builder /app/pnpm-workspace.yaml ./
COPY --from=builder /app/eslint.config.mjs ./
COPY --from=builder /app/.eslintrc.json ./
COPY --from=builder /app/.npmrc ./
COPY --from=builder /app/turbo.json ./
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/agent ./agent
COPY --from=builder /app/client ./client
COPY --from=builder /app/lerna.json ./
COPY --from=builder /app/packages ./packages
COPY --from=builder /app/scripts ./scripts
COPY --from=builder /app/characters ./characters

# Expose necessary ports
EXPOSE 3000 5173

# Command to start the application
CMD ["sh", "-c", "pnpm start & pnpm start:client"]

I need to run the start command with args pointing to custom application configuation files, but coolify doesn't seem to support this. As it stands it seems I'll have to fork the repo and create a branch for the coolify script; ideally I'd prefer not to do this/I imagine there may be situations where others are working with closed source code that a client doesn't want leaving the gh org. Seems like fairly basic functionality to include, and could simply copy-paste the interface for overwriting docker-composes to include dockerfiles.