Use docker run command to pass arguments to CMD in Dockerfile

by

Make sure your Dockerfile declares an environment variable with ENV:

ENV environment default_env_value
ENV cluster default_cluster_value

The ENV <key> <value> form can be replaced inline.

Then you can pass an environment variable with docker run. Note that each variable requires a specific -e flag to run.

docker run -p 9000:9000 -e environment=dev -e cluster=0 -d me/app

Or you can set them through your compose file:

node:
  environment:
    - environment=dev
    - cluster=0

Your Dockerfile CMD can use that environment variable, but, as mentioned in issue 5509, you need to do so in a sh -c form:

CMD ["sh", "-c", "node server.js ${cluster} ${environment}"]

The explanation is that the shell is responsible for expanding environment variables, not Docker. When you use the JSON syntax, you’re explicitly requesting that your command bypass the shell and be executed directly.

Same idea with Builder RUN (applies to CMD as well):

Unlike the shell form, the exec form does not invoke a command shell.
This means that normal shell processing does not happen.

For example, RUN [ "echo", "$HOME" ] will not do variable substitution on $HOME. If you want shell processing then either use the shell form or execute a shell directly, for example: RUN [ "sh", "-c", "echo $HOME" ].

When using the exec form and executing a shell directly, as in the case for the shell form, it is the shell that is doing the environment variable expansion, not docker.

More Related Contents:

  1. How to cache the RUN npm install instruction when docker build a Dockerfile
  2. Docker-compose: node_modules not present in a volume after npm install succeeds
  3. ECONNREFUSED for Postgres on nodeJS with dockers
  4. MongoDB on with Docker “failed to connect to server [localhost:27017] on first connect “
  5. Docker – SequelizeConnectionRefusedError: connect ECONNREFUSED 127.0.0.1:3306
  6. How to set npm credentials using `npm login` without reading from stdin?
  7. Error: Redis connection to 127.0.0.1:6379 failed – connect ECONNREFUSED 127.0.0.1:6379
  8. Why does `package-lock.json` causes a failure in a docker container build when `npm install`?
  9. Why COPY package*.json ./ precedes COPY . .?
  10. How to install nvm in docker?
  11. Is there a way to make npm install (the command) to work behind proxy?
  12. How do you turn a Mongoose document into a plain object?
  13. Add a volume to Docker, but exclude a sub-folder
  14. How to edit a node module installed via npm?
  15. Setting expiry time for a collection in mongodb using mongoose
  16. Create a HOC (higher order component) for authentication in Next.js
  17. node.js – request – How to “emitter.setMaxListeners()”?
  18. Proxy with express.js
  19. How do I host multiple Node.js sites on the same IP/server with different domains?
  20. Redirect all trailing slashes globally in express
  21. Read remote file with node.js (http.get)
  22. How to use http.client in Node.js if there is basic authorization
  23. Conditional ENV in Dockerfile
  24. Global npm install location on windows?
  25. How to open a create-react-app from another computer connected to the same network?
  26. How to enable BLOB-logging for a Node.js Api App on Azure?
  27. Gatsby Failed Build – error “window” is not available during server side rendering
  28. npm: Why is a version “0.1” invalid?
  29. How to catch an ENOENT with nodejs child_process.spawn?
  30. What’s the difference between dependencies, devDependencies, and peerDependencies in NPM package.json file?

Leave a Comment