Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem vith elasticsearch .env "unexpected character" #597

Closed
artmouse opened this issue Dec 20, 2021 · 5 comments · Fixed by #598
Closed

Problem vith elasticsearch .env "unexpected character" #597

artmouse opened this issue Dec 20, 2021 · 5 comments · Fixed by #598

Comments

@artmouse
Copy link

Description
unexpected character "." in variable name near "discovery.type=single-node\n\n# Set custom heap size to avoid memory errors\nES_JAVA_OPTS=-Xms1g -Xmx1g\n\n# Avoid test failures due to small disks\n# More info at https://github.com/markshust/docker-magento/issues/488\ncluster.routing.allocation.disk.threshold_enabled=false\nindex.blocks.read_only_allow_delete\n"

@torhoehn
Copy link
Contributor

torhoehn commented Dec 20, 2021

Yes, got the same error while creating a new project.

See 7f2cbce

The environment variables aren't working as env_file. I'll create a PR to rollback this change.

@petskratt
Copy link

The reason it does not work: shell variable name can contain [a-zA-Z0-9_] but not dot.

Bash gives "env/elasticsearch.env: line 4: discovery.type=single-node: command not found" (to make issue findable by this error message as well)

@markshust
Copy link
Owner

Sorry about this! That's what happens when I make changes and forget to test a new config myself. Thanks @torhoehn for the PR, this should be all fixed.

@encryptblockr
Copy link

The reason it does not work: shell variable name can contain [a-zA-Z0-9_] but not dot.

Bash gives "env/elasticsearch.env: line 4: discovery.type=single-node: command not found" (to make issue findable by this error message as well)

so why are we using dots in variable name if not supported with shell variable name?!!!?

@encryptblockr
Copy link

Sorry about this! That's what happens when I make changes and forget to test a new config myself. Thanks @torhoehn for the PR, this should be all fixed.

your MR does not work with using env_file: with docker-compose

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants