Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
invalid variable names in docker/elasticsearch/env/docker.env when using docker compose v2
See original GitHub issueInstalling the latest docker compose (v2) will cause the dev.sh script to throw errors:
unexpected character "." in variable name near "discovery.type=single-node\nxpack.security.enabled=false\nES_JAVA_OPTS=-Xms256m -Xmx256m -Dlog4j2.formatMsgNoLookups=true\n"
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (3 by maintainers)
Top Results From Across the Web
invalid variable names in docker/elasticsearch/env ... - GitHub
Installing the latest docker compose (v2) will cause the dev.sh script to throw errors: unexpected character "." in variable name near ...
Read more >Docker Compose - invalid variable - Stack Overflow
Check that your environment variables or .env file does not contain multiline variables (e.g. SSH keys). After flattening them, error should ...
Read more >Bug 49647 – Do not use environment variables names with ...
For multi container apps the App Center adds a bunch of environment variables to the compose file before it is used by Docker...
Read more >Nginx reverse proxy with variable names for docker container ...
The whole reason is: I have like 10 docker-compose files with 10 wordpress stacks with 3 containers each (apache+php / mariabdb / phpmyadmin) ......
Read more >How to unset an invalid environment variable in bash?
This may be easier to understand without docker and other confusions. You have an environment variable with an "odd" name that you want...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
On macos, I had to run
docker-compose disable-v2so that my docker-compose didn’t run on v2. See https://docs.docker.com/compose/cli-command/#install-on-mac-and-windowsThis issue was closed because it has been inactive for 30 days since being marked as stale.