You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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 :)
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.
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 usingunik build
returns a connection refused error:Furthermore, the documentation states the daemon running on port 3000, so does the
unik build
command by default. However when launching theunik daemon
, the application states the daemon as listening on port 9967.Changing the port of the
unik build
command yields the same error regardless.The text was updated successfully, but these errors were encountered: