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

Docker binaries are not statically linked, so using 'scratch' in the Docker files results in error #1765

Closed
ylebre opened this issue Jun 4, 2021 · 0 comments
Assignees

Comments

@ylebre
Copy link
Contributor

ylebre commented Jun 4, 2021

The docker images built using Dockerfile.reva and Dockerfile.revad end in an error:

standard_init_linux.go:211: exec user process caused "no such file or directory"

The cause seems to the compiled reva and revad binaries are not statically linked.

Adding env CGO_ENABLED lets the compiler generate a statically linked binary.
After this change, running the docker image results in

nothing to do, no grpc/http enabled_services declared in config

which makes sense because the passed configuration file is empty.

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