{"action":"created","issue":{"url":"https://api.github.com/repos/emc-advanced-dev/unik/issues/98","repository_url":"https://api.github.com/repos/emc-advanced-dev/unik","labels_url":"https://api.github.com/repos/emc-advanced-dev/unik/issues/98/labels{/name}","comments_url":"https://api.github.com/repos/emc-advanced-dev/unik/issues/98/comments","events_url":"https://api.github.com/repos/emc-advanced-dev/unik/issues/98/events","html_url":"https://github.com/emc-advanced-dev/unik/issues/98","id":184183658,"number":98,"title":"Issue while starting unik daemon in docker-machine setup","user":{"login":"hanneslehmann","id":9842483,"avatar_url":"https://avatars.githubusercontent.com/u/9842483?v=3","gravatar_id":"","url":"https://api.github.com/users/hanneslehmann","html_url":"https://github.com/hanneslehmann","followers_url":"https://api.github.com/users/hanneslehmann/followers","following_url":"https://api.github.com/users/hanneslehmann/following{/other_user}","gists_url":"https://api.github.com/users/hanneslehmann/gists{/gist_id}","starred_url":"https://api.github.com/users/hanneslehmann/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hanneslehmann/subscriptions","organizations_url":"https://api.github.com/users/hanneslehmann/orgs","repos_url":"https://api.github.com/users/hanneslehmann/repos","events_url":"https://api.github.com/users/hanneslehmann/events{/privacy}","received_events_url":"https://api.github.com/users/hanneslehmann/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-10-20T09:50:47Z","updated_at":"2016-10-20T15:09:47Z","closed_at":null,"body":"Hello,\r\n\r\nI think i successfully have build the unik binary, but I have some issues in starting it. Actually I am on Ubuntu, but running docker in a seperate virtual machine for security reasons, no fancy setup, just using docker-machine. The binary already ended up within the docker-machine \"default\", I copied it to my local, bare-metal machine, I can execute it by calling:\r\n`unik daemon --debug --trace --logfile logs.txt`\r\n\r\nBut then I get the error:\r\n```\r\nDEBU[0013] util.LogCommand.func2[util/log.go:95]\r\n./gomaincaller.go:20[/tmp/go-build882971369/command-line-arguments/_obj/gomaincaller.cgo1.go:26]: undefined: main \r\nERRO[0013] main.main[unik/unik.go:9]\r\ncobra.(*Command).Execute[cobra/command.go:618]\r\ncobra.(*Command).ExecuteC[cobra/command.go:662]\r\ncobra.(*Command).execute[cobra/command.go:572]\r\ncmd.glob.func5[cmd/daemon.go:91]\r\nrunning daemon failed: [cmd/daemon.go:86] daemon failed to initialize: {[daemon/daemon.go:106] initializing virtualbox provider: {[virtualbox/virtualbox_provider.go:49] deploying virtualbox instance listener: {[virtualbox/deploy_instance_listener.go:39] compiling instance listener source to unikernel: {exit status 2}}}}\r\n[logs.txt](https://github.com/emc-advanced-dev/unik/files/541336/logs.txt)\r\n\r\n```\r\n\r\nAs I still don't have the understanding how virtualbox, docker, unik are playing together, I don't know where the issue could be."},"comment":{"url":"https://api.github.com/repos/emc-advanced-dev/unik/issues/comments/255134478","html_url":"https://github.com/emc-advanced-dev/unik/issues/98#issuecomment-255134478","issue_url":"https://api.github.com/repos/emc-advanced-dev/unik/issues/98","id":255134478,"user":{"login":"ilackarms","id":5974898,"avatar_url":"https://avatars.githubusercontent.com/u/5974898?v=3","gravatar_id":"","url":"https://api.github.com/users/ilackarms","html_url":"https://github.com/ilackarms","followers_url":"https://api.github.com/users/ilackarms/followers","following_url":"https://api.github.com/users/ilackarms/following{/other_user}","gists_url":"https://api.github.com/users/ilackarms/gists{/gist_id}","starred_url":"https://api.github.com/users/ilackarms/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ilackarms/subscriptions","organizations_url":"https://api.github.com/users/ilackarms/orgs","repos_url":"https://api.github.com/users/ilackarms/repos","events_url":"https://api.github.com/users/ilackarms/events{/privacy}","received_events_url":"https://api.github.com/users/ilackarms/received_events","type":"User","site_admin":false},"created_at":"2016-10-20T15:09:47Z","updated_at":"2016-10-20T15:09:47Z","body":"in the last error it looks like you don't have a properly configured `daemon-config.yaml`. this file should live at  `~/.unik/daemon-config.yaml` on the machine where you're running the daemon. you can also put this file in a custom location and point to it with `unik daemon --f <path/to/daemon-cfg>`\r\n\r\nunik is booting with 0 providers configured (hence the error `virtualbox is not a known provider. Available: }`. if you are running unik on the docker-machine vm, you won't be able to use virtualbox as a provider (since it requires virtualbox to be running on the host).\r\n\r\ntwo solutions are, either:\r\n1 - run unik on the same machine where you have virtualbox running (and add virtualbox to your `daemon-config.yaml`, as per the instructions here: https://github.com/emc-advanced-dev/unik/blob/master/docs/providers/virtualbox.md)\r\n\r\n2 - use a provider that targets a remote hypervisor, such as AWS, Vsphere, or Openstack (probably not what you are looking for)"}}
{"actor":{"display_login":"ilackarms"}}