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

$PATH lost to Standard Bundles #839

Closed
geowa4 opened this issue Jul 6, 2016 · 0 comments · Fixed by operable/go-relay#37
Closed

$PATH lost to Standard Bundles #839

geowa4 opened this issue Jul 6, 2016 · 0 comments · Fixed by operable/go-relay#37
Assignees
Milestone

Comments

@geowa4
Copy link

geowa4 commented Jul 6, 2016

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

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.

@kevsmith kevsmith added this to the Cog 0.11.0 milestone Jul 12, 2016
@vanstee vanstee modified the milestones: Cog 0.11.0, 0.12.0 Jul 19, 2016
@kevsmith kevsmith modified the milestones: Cog 0.12.0, Cog 0.13.0 Aug 4, 2016
@mpeck mpeck self-assigned this Aug 17, 2016
@mpeck mpeck added the review label Aug 17, 2016
@mpeck mpeck removed the review label Aug 17, 2016
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.

4 participants