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

Can't start stack with timescaledb checked: services.timescaledb.environment contains an invalid type, it should be an object, or an array #232

Closed
KlausHans opened this issue Jan 10, 2021 · 0 comments · Fixed by #578

Comments

@KlausHans
Copy link

If i try to start (aka docker compose) my stack with timescaledb checked i get this error:

ERROR: The Compose file './docker-compose.yml' is invalid because:
services.timescaledb.environment contains an invalid type, it should be an object, or an array

In the yaml file the environment of timescale is specified as

environment: POSTGRES_USER=timescaleuser POSTGRES_PASSWORD=%randomPassword% POSTGRES_DB=postdb

This is obviously wrong syntax. If i change it by hand to

    environment:
    - POSTGRES_USER=timescaleuser
    - POSTGRES_PASSWORD=%randomPassword%
    - POSTGRES_DB=postdb

docker compose works.

ukkopahis added a commit to ukkopahis/IOTstack that referenced this issue Jun 19, 2022
Implements and resolves SensorsIot#232

Also changes user to reflect the strong recommendation of SensorsIot#287

As %randomPassword% doesn't seem to work, change to use the default
password as listed on Default-Configs.md.

Change default public port from 5433 to avoid port-conflict with posgresql.
ukkopahis added a commit to ukkopahis/IOTstack that referenced this issue Jun 25, 2022
Implements and resolves SensorsIot#232

Also changes user to reflect the strong recommendation of SensorsIot#287

As %randomPassword% doesn't seem to work, change to use the default
password as listed on Default-Configs.md and add support for SensorsIot#505
style variables.

Change default public port from 5433 to avoid port-conflict with posgresql.
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.

1 participant