cetic / unikernels

Unikernel and immutable infrastructures
582 stars 47 forks source link

Unik: Connection refused while trying create sample unikernel applications #2

Closed GaetanLongree closed 5 years ago

GaetanLongree commented 6 years ago

After installing and attempting to run a sample unikernel application following the Run your first C++ unikernel guide, launching the unik daemon and attempting to build any code using unik build returns a connection refused error:

ERRO[0000] build failed: [cmd/build.go:105] building image failed: {[client/images.go:60] request failed: {[lxhttpclient/httpclient.go:339] error performing post request: {Post http://localhost:3000/images/myImage/create?base=rump&lang=nodejs&provider=virtualbox&args=&mounts=&force=false&no_cleanup=false: dial tcp [::1]:3000: getsockopt: connection refused}}}

Furthermore, the documentation states the daemon running on port 3000, so does the unik build command by default. However when launching the unik daemon, the application states the daemon as listening on port 9967. Changing the port of the unik build command yields the same error regardless.

theKAKAN commented 5 years ago

Please create the issue at Unik's Github repository
This is a place for just general reference to what Unikernels are, what they do, how they are useful to us and the currently on going projects.
It's the wrong place to ask help for a project :)

GaetanLongree commented 5 years ago

As mentioned in §1 of Choice of Unikernel Solution, an issue is already present on the Unik's repository (see issue #152). Albeit slightly different (I tested Java, the issue #152 relates to Node,js) the underlying problem is the same.

This project was my university thesis during an internship at CETIC and it was decided to have issues related to the thesis' progression submitted both to this repository and the concerning project's repository.

banzo commented 5 years ago

for clarity reasons, I'll close this issue.