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

environment variable name 'ENV MB_DB_TYPE' may not contain whitespace #1

Closed
kyleneese opened this issue Jan 29, 2020 · 7 comments
Closed

Comments

@kyleneese
Copy link

kyleneese commented Jan 29, 2020

Running sudo docker-compose up -d after filling in the default .env file values produces the following error:

$ sudo docker-compose up -d
ERROR: In file /Users/<user>/compose-postgres-metabase/config/metabase_database.env: environment variable name 'ENV MB_DB_TYPE' may not contain whitespace.

Removing ENV from the vars in config/metabase_database.env appears to resolve this.

@rbashish
Copy link

rbashish commented Feb 24, 2020

well I also encountered the exactly same error. Tried removing ENV and then it began setup.
After the setup complete, I was not able to access :3000.

I waited for sometime around 5min and voila I get the page showing:
metabase

And most of the time it is showing error connection refused.
The setup works well with localhost

@rbashish
Copy link

On checking the logs, I found that there is a problems with the postgres connection on 54320 port and because of this I am getting connection refused.

@bbarman4u
Copy link

@rbashish what did you do to resolve the issue?

@lucasfcnunes
Copy link

@bbarman4u see #2

@Tinitto
Copy link
Owner

Tinitto commented Mar 30, 2021

There seems to be a change in how env files are read in docker-compose 1.24.0 as opposed to <1.24.0 according to docker/compose#6951. Removing 'ENV' messes things up.

Maybe someone can look at updating this to work with docker-compose >=1.24.0

@Tinitto
Copy link
Owner

Tinitto commented Mar 31, 2021

@rbashish , @bbarman4u, looks like the issue you were facing was coming from not using a fully qualified hostname as specified in the metabase docker docs
image

Could you try with the actual host of the server. Localhost may not work as expected.

@Tinitto
Copy link
Owner

Tinitto commented Mar 26, 2022

Closing issue due to inactivity

@Tinitto Tinitto closed this as completed Mar 26, 2022
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