You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears the container's PATH is messed up when running container bundles through Relay. I was using the golang:onbuild image to quickly prototype my bundle. In it, I placed some simple scripts for each of my commands. For example, I would have /usr/local/bin/custom-command with contents
#!/usr/bin/env bash
set -e
/usr/local/bin/go-wrapper run custom-command
The error message I get back is
+ exec app private-list
/usr/local/bin/go-wrapper: 89: exec: app: not found
It appears the container's
PATH
is messed up when running container bundles through Relay. I was using thegolang:onbuild
image to quickly prototype my bundle. In it, I placed some simple scripts for each of my commands. For example, I would have/usr/local/bin/custom-command
with contentsThe error message I get back is
app
is an executable located in$GOPATH/bin
, which is added to$PATH
here: https://github.com/docker-library/golang/blob/ce284e14cdee73fbaa8fb680011a812f272eae2e/1.6/Dockerfile#L21. If I switch my shell script to execute the Go binary directly (/go/bin/app custom-command
) all works well.I have not checked if other environment variables are lost.
The text was updated successfully, but these errors were encountered: