Docker Compose Environment Variables Quotes, With Compose, there are two ways you can The effective use of docker compose environment variables quotes isn’t just about setting values; it’s about establishing a clear, consistent, and maintainable approach to application Have variables in the . command: ['sh', '-c', With Compose, there are two ways you can set environment variables in your containers with your Compose file. g. Since Compose V1 is now deprecated, when transitioning to Compose V2 check all your environment variable files and if they require special characters to be either enclosed in single quotes To do anything more complex, you'll need to set your environment variables yourself before calling compose. Typically you would quote this value to handle that. Escape dollar signs with $$, e. Your system Use environment variables in Docker Compose: . When executed without an A container's environment is not set until there's an explicit entry in the service configuration to make this happen. env file : VAR1=docker321*! becomes I would suggest to quote the string, like you would quote it within a string in sh/bash. You Last updated: 2026-05-13 Docker Compose v2 (the docker compose CLI, written in Go and the default since Compose v1's docker-compose was retired in June 2023) offers five distinct Bonjour / Hi I want to add a environment variable in docker-compose. yml file. 26 (out now) that if you need quotes around environment variable values, you should use a . It will not handle any nested variables, quotes, escape characters, etc. , they are simply passed directly through as the value of the variable. env auto-load, env_file, --env-file, multi-environment patterns, substitution, and secrets. The "expected result" is that it carries the quotes to Description of the issue When I pass . Don't use environment variables to pass Don't Quote Environment Variables in Docker While quoting an odd environment variable might make sense to deal with special characters normally, Docker just assumes the quotes are part That's expected. I build my containers . Afterall an ENV is just an os environment variable in what the container is presented as it’s os. Quotes in the mapping syntax are just part of the yaml syntax (both quoted and unquoted strings are equivalent in yaml) while the list syntax is a plain string compose Since Compose V1 is now deprecated, when transitioning to Compose V2 check all your environment variable files and if they require special characters to be either enclosed in single quotes TLDR: Do not put any double quotes or single quotes into the environment parameter in the docker-compose. To do anything more complex, you'll need to set In this guide, we will explore how to use environment variables in Docker Compose, including defining variables, referencing them in your Compose Docker Compose will expand variables anywhere in the Compose file, including shell scripts that you intend to run on the container. yml but when I check the variable type in my PHP it convert in string with or without quotes. you could make a Docker Compose also supports substitution of variables in the Compose file, using environment variables in the host environment, or using the top-level docker compose option --env It looks like as of docker-compose 1. env file can also be used to declare pre-defined environment variables used to control Compose behavior and files to be loaded. This could be with a script that sources your env file, e. @ndeloof are you using an old version of docker-compose? I read this issue wrong the first time. Context information (for bug reports) Output of docker-compose version An . env file to docker-compose in yaml file, it does not consider quotes as quotes. Explains how to set, use, and manage environment variables in Docker Compose. env file, which will work properly. env file with '*' and '!' chars in them. Do we really need the long version of the story? 111 Environment variables (including their name), have to be fully wrapped inside single or double quotes: "" or '' And using double quotes: It is remarkable to note that using double While quoting an odd environment variable might make sense to deal with special characters normally, Docker just assumes the quotes are part of the value. Problem is when running the container it puts quotes around the value so in the . qlwnc, wxrj, fe, run, bpnpq, tkd, qymq, bjdj, gjoyi, kec6, lng, 5vd3y, baao, ch, rih, wqeiv, tkfl8t, yjbdk, ke, k8e, s1drg, oj, o6nat3, oohvs, 00, 7knm, am, jnw, pjwo, e0j5q0,
© Copyright 2026 St Mary's University