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

Error when launching via docker-compose #18

Open
Sikksens opened this issue Jun 30, 2022 · 7 comments
Open

Error when launching via docker-compose #18

Sikksens opened this issue Jun 30, 2022 · 7 comments

Comments

@Sikksens
Copy link

Hey there,

When launching via docker-compose I get the error error="field not found, node: postgres"

image

@zekroTJA
Copy link
Owner

zekroTJA commented Jul 1, 2022

Hey. It seems like you are passing your Postgres configuration directly via the key postgres though the configuration key is database.postgres.

Please take a look at the example configuration file or at the example Docker Compose setup for reference.

@Sikksens
Copy link
Author

sorry for the late reply, I'm fairly new to Docker, I'm using your default docker-compose setup with the obvious changed keys but can't figure out where the postgres key is set?

@zekroTJA
Copy link
Owner

zekroTJA commented Nov 2, 2022

postgres is the name of the database node in the config, like in database.postgres.host for example. You can see it here as well. When using environment variables, the nodes are separated by underscores (_) like shown here. Maybe you have a miss-configuration there which is causing the issue.

@OBenned
Copy link

OBenned commented Mar 6, 2023

I get the same error using docker-compose.
Tried with the default docker-compose values but get the following error from minio:

minio_1 | ERROR Unable to validate credentials inherited from the shell environment: Invalid credentials minio_1 | > Please provide correct credentials minio_1 | HINT: minio_1 | Access key length should be at least 3, and secret key length at least 8 characters

and yuri:

yuri69_1 | FATA[2023/03/06 19:25:21 UTC] Config parsing failed error="field not found, node: postgres"

@OBenned
Copy link

OBenned commented Mar 6, 2023

I fixed the minio part, but the error from yuri is still there

@zekroTJA
Copy link
Owner

Well, I figured out what the problem was with the provided docker-compose.yml. The image used for yuri in the file was just set to a very old image and not to the new one hosted on GHCR. Therefore, the PostgreSQL database driver was not implemented yet in this version and though the setup would fail because also the config node was not existent because of that.

Now, I've updated the docker-compose.yml and everything should run smoothly. Sorry for my late response on this topic. :)

@OBenned
Copy link

OBenned commented Mar 29, 2023

No worries and thank you for that :)

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

No branches or pull requests

3 participants