-
Notifications
You must be signed in to change notification settings - Fork 149
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
exec user process error #173
Comments
I think I see the problem. Let me test a fix and get back to you. |
kfdm
added a commit
to kfdm/promgen
that referenced
this issue
Aug 19, 2019
- Change docker-entrypoint to use /bin/sh - Leave mariadb-dev and postgressql-dev installed for shared libraries Fixes line#173
kfdm
added a commit
to kfdm/promgen
that referenced
this issue
Aug 20, 2019
- Change docker-entrypoint to use /bin/sh - Leave mariadb-dev and postgressql-dev installed for shared libraries - Fix alertmanager config Fixes line#173
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On a linux mint installation, I run docker-compose up on a freshly cloned repo, and get many errors from standard_init_linux.go about exec user process.
Console output:
Following steps from https://hub.docker.com/r/kfdm/promgen/ also results in standard_init_linux.go:190: exec user process caused "no such file or directory" error at the end of the first Docker domand.
Is there a missing step in the installation guide for proper configuration?
The text was updated successfully, but these errors were encountered: