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

Crash on start #104

Closed
R0GGER opened this issue Sep 23, 2020 · 1 comment · Fixed by #105
Closed

Crash on start #104

R0GGER opened this issue Sep 23, 2020 · 1 comment · Fixed by #105

Comments

@R0GGER
Copy link

R0GGER commented Sep 23, 2020

CLI:
docker run -d --name yacht --restart=always -p 8001:8000 -v /var/run/docker.sock:/var/run/docker.sock -v path-to/yacht:/config selfhostedpro/yacht

Error:

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
nginx: [emerg] open() "/config/nginx/nginx.conf" failed (2: No such file or directory)
[services.d] done.
nginx: [emerg] open() "/config/nginx/nginx.conf" failed (2: No such file or directory)
INFO:     Started server process [265]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on unix socket /tmp/gunicorn.sock (Press CTRL+C to quit)
nginx: [emerg] open() "/config/nginx/nginx.conf" failed (2: No such file or directory)
nginx: [emerg] open() "/config/nginx/nginx.conf" failed (2: No such file or directory)
nginx: [emerg] open() "/config/nginx/nginx.conf" failed (2: No such file or directory)
nginx: [emerg] open() "/config/nginx/nginx.conf" failed (2: No such file or directory)

@SelfhostedPro
Copy link
Owner

Currently building a dev image that should resolve this. Originally I was making the nginx.conf in the /config directory which is what was causing this issue.

Once dev is built and tested. I'll link the PR into master and when that's closed you should be good to go.

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.

2 participants