The executables build successfully. However building a docker image through waypoint build, fails because waypoint can not locate the ceb binary, that got embedded into the executable through go-bindata. Waypoint tries to inject this binary into the docker image to capture logs and enable remote access to container instances.

• Output: https://gist.github.com/winpat/321145ab42bb5bddba7ea0adc66777b0
• Error handling in waypoint: https://github.com/hashicorp/waypoint/blob/main/builtin/docker/builder.go#L184
• Error handling in go-bindata: https://github.com/jteeuwen/go-bindata/blob/master/testdata/out/debug.go#L113

I've tried to find similar issues in the issue tracker with regards to go-bindata and nix, but could not find anything.

In the fixup phase, patchelf issues a warning (which could just be because the executables are statically compiled):

post-installation fixup
patching script interpreter paths in /nix/store/jzzmajkvqrqq4sdjplj1afs5vr6wy399-waypoint-0.1.2
checking for references to /build/ in /nix/store/jzzmajkvqrqq4sdjplj1afs5vr6wy399-waypoint-0.1.2...
patchelf: cannot find section '.dynamic'. The input file is most likely statically linked
building '/nix/store/qdk4xv52v2g60dgc5jnvmmd1vk9c7pvx-user-environment.drv'...
created 101 symlinks in user environment

I've toyed with dontFixup and dontStrip without any success. Maybe @kalbasit has an idea on what I could try next?

I also created an issue in the upstream repository. They appear to use Nix to manage their go dependencies but not for the build itself.

hashicorp/waypoint#614

Closing in favour of #103754