Issue Running "hab studio enter" in Tutorial (Unknown Studio Command)


#1

When following the tutorial, I am unable to progress past step 5 due to an error running hab studio enter.

Output is as follows:

$ RUST_LOG=debug hab studio enter
DEBUG 2018-08-22T16:25:15Z: habitat_common::ui: UI { shell: Shell { input: InputStream { isatty: true }, out: OutputStream { coloring: Auto, isatty: true, is_colored(): true, supports_color(): true }, err: OutputStream { coloring: Auto, isatty: true, is_colored(): true, supports_color(): true } } }
DEBUG 2018-08-22T16:25:15Z: hab::config: Loading CLI config from /Users/siraj/.hab/etc/cli.toml
DEBUG 2018-08-22T16:25:15Z: hab::command::studio::enter: Setting default origin sirajrauff via CLI config
DEBUG 2018-08-22T16:25:15Z: hab::command::studio::enter: Setting HAB_CACHE_KEY_PATH=/Users/siraj/.hab/cache/keys
DEBUG 2018-08-22T16:25:15Z: hab::command::studio::enter: Setting ARTIFACT_PATH=/Users/siraj/.hab/cache/artifacts
DEBUG 2018-08-22T16:25:15Z: hab::command::studio::docker: Running command: "/usr/local/bin/docker" "version" "--format=\'{{.Server.Os}}\'"
DEBUG 2018-08-22T16:25:15Z: hab::analytics: Event: v=1&tid=UA-6369228-7&cid=03090537-e5dc-4008-8c4f-1ec96788ac99&t=event&aip=1&an=hab&av=0.61.0%2F20180815171832&ds=cli--hab&ec=invoke&ea=hab--studio--enter
DEBUG 2018-08-22T16:25:15Z: hab::analytics: Creating directory /Users/siraj/.hab/cache/analytics
DEBUG 2018-08-22T16:25:15Z: hab::analytics: Creating file /Users/siraj/.hab/cache/analytics/event-1534955115.577933000.txt
DEBUG 2018-08-22T16:25:15Z: hab::command::studio::docker: Running command: "/usr/local/bin/docker" "images" "habitat/default-studio:0.61.0" "-q"
DEBUG 2018-08-22T16:25:15Z: hab::command::studio::docker: Found Studio Docker image locally.
DEBUG 2018-08-22T16:25:15Z: hab::command::studio::docker: Running command: "/usr/local/bin/docker" "version" "--format=\'{{.Server.Os}}\'"
DEBUG 2018-08-22T16:25:15Z: hab::command::studio::docker: Running command: "/usr/local/bin/docker" "version" "--format=\'{{.Server.Os}}\'"
DEBUG 2018-08-22T16:25:15Z: hab::command::studio::docker: Running command: "/usr/local/bin/docker" "version" "--format=\'{{.Server.Os}}\'"
DEBUG 2018-08-22T16:25:15Z: hab::command::studio::docker: Running command: "/usr/local/bin/docker" "version" "--format=\'{{.Server.Os}}\'"
DEBUG 2018-08-22T16:25:17Z: habitat_core::os::process::imp: Calling execvp(): ("/usr/local/bin/docker") ["start", "--interactive", "Users--siraj--git-repos--sample-node-app"]
   hab-studio: No secret keys imported! Did you mean to set HAB_ORIGIN?
To specify a HAB_ORIGIN, either set the HAB_ORIGIN environment
variable to your origin name or run 'hab setup' and specify a
default origin.
   hab-studio: Exported: HAB_ORIGIN=siraj
Unknown Studio Command
$

Immediately I notice that the debug line near the end that specifies HAB_ORIGIN=siraj is not the same as is being read through the config file, the one which I had setup on a previous step through the cli setup command.

Checking ~/.hab/etc/cli.toml I see:
origin = "sirajrauff"

And in the project’s /habitat/plan.sh I see:
pkg_origin=sirajrauff

I’ve checked that the keys exist in ~/.hab/cache/keys, prefixed with the origin, and I have correctly setup the builder account and the auth key is the key generated through my profile page.

Currently on the latest version, installed through homebrew.

$ hab --version
hab 0.61.0/20180815171832

#2

Note: Downgraded versions using the install.sh script, and it is now working as intended.

$ hab --version
hab 0.59.0/20180712162348

#3

This is a known issue with the 0.61.0 studio and will be fixed in 0.62.0. The 0.61.0 studio is not looking in the right place for keys regardless of what your HAB_ORIGIN var or `cli setup specifies.


#4

@mwrock thanks for the response. Is this issue being tracked anywhere? I had gone through the GitHub issues page, as well as searched quite a bit on stack overflow and could not find anything related.

Notably, I found that I was able to run the example correctly with version 0.61.0 on a linux box so I had thought this was a configuration issue on my end.


#5

I suppose the issue title does not make it obvious, but it is #5494. The issue impacts the docker based linux studio. A native studio on a Linux host should not experience this problem which explains why you were able to get by on Linux.

We hope to release the fix next week.