Closed kplimack closed 4 years ago
Currently you can't use an exporter in OSX, it must be run from linux or in the studio. With that said I think we could do more here to alert you to that fact.
Moving to the backlog to discuss adding a more helpful failure message.
This is running in a Studio on MacOS (it's actually impossible to run the Docker exporter natively on MacOS).
Another user has reported this same issue in Slack, but I have so far not been able to replicate it locally. However, it appears to be a binlinking issue. The other user had a Go app, with no runtime dependencies, and a (mistakenly) empty pkg_bin_dirs
entry. This basically meant there was nothing to link in the link_user_pkgs
after the cacerts directory was linked (that happens fine).
Once the user added a directory to pkg_bin_dirs
, the export process continued normally.
Versions at play:
core/hab/0.55.0/20180321215236
core/hab-pkg-export-docker/0.55.0/20180321215219
@fnichol Does this seem like something you've addressed in recent changes you've been making with the binlinking logic?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.
When I attempt to export anything to docker, I break on cacerts.
tldr:
[x] The OS (including version) where you are running any of the Habitat commands.
mac_os_x => 10.13.3
[x] Debug/backtrace of the command you are trying to run. You can set the following environment variables before running the
hab
command to generate a trace:[x] Current Habitat environment variables where the
hab
command or supervisor is running. These can be gathered using: