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

hab studio enter fails on mac os x #1178

Closed
dee-kryvenko opened this issue Aug 21, 2016 · 4 comments
Closed

hab studio enter fails on mac os x #1178

dee-kryvenko opened this issue Aug 21, 2016 · 4 comments

Comments

@dee-kryvenko
Copy link

OS: Mac OS X 10.11.6

Habitat version is 0.9.0/20160816000307, has been installed with brew cask install hab.
env | grep -i HAB shows nothing.

Docker is 1.12.0-a, the new one that works without virtualbox.

Actual error:

DEBUG:hab::command::studio::inner: Propagating environment variable into container: HAB_ORIGIN=llibicpep
DEBUG:hab::exec: Calling execv: ("/usr/local/bin/docker") ["run", "--rm", "--tty", "--interactive", "--privileged", "--env", "HAB_ORIGIN=llibicpep", "--volume", "/var/run/docker.sock:/var/run/docker.sock", "--volume", "/Users/llibicpep/.hab/cache/keys:/hab/cache/keys", "--volume", "/Users/llibicpep/repos/tc/canary-nodejs:/src", "habitat-docker-registry.bintray.io/studio", "enter"]
   hab-studio: Creating Studio at /hab/studios/src (default)
   hab-studio: Importing llibicpep secret origin key
» Importing origin key from standard input
★ Imported secret origin key llibicpep-20160821134452.
   hab-studio: Entering Studio at /hab/studios/src (default)
   hab-studio: Exported: HAB_ORIGIN=llibicpep
   hab-studio: Exported: no_proxy=*.local, 169.254/16

/hab/pkgs/core/coreutils/8.25/20160729192409/bin/env: '169.254/16': No such file or directory
@bookshelfdave
Copy link
Contributor

This is resolved by unsetting the no_proxy environment variable.

@dee-kryvenko
Copy link
Author

Yup thanks, was able to workaround this by cleaning Docker Preferences in Advanced->Exclude field. So maybe this is the issue in the way how Docker populating no_proxy variable, not sure though.

@bookshelfdave
Copy link
Contributor

We have a fix here, which will be available in the next release.

@dee-kryvenko
Copy link
Author

Great! Thank you!

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

2 participants