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
{{ message }}
This repository has been archived by the owner on Jul 17, 2023. It is now read-only.
Describe the bug
Right now when you build an application it will use the name convention from the parent directory of that application, instead of using the name from kraft.yaml. This bug also caused this problem #80 .
To Reproduce
Steps to reproduce the behavior: [email protected]:unikraft/app-helloworld.git
2. cd app-helloworold
3. kraft configure -p kvm -m x86_64
4. kraft build
Expected behavior
After building an application with the name example from kraft.yaml, the unikernel executable should have the name example_kvm-x86-64 even though the parent directory where this application has a different name.
Screenshots
Desktop (please complete the following information):
OS: Ubuntu
Version 20.10
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
Right now when you build an application it will use the name convention from the parent directory of that application, instead of using the name from
kraft.yaml
. This bug also caused this problem #80 .To Reproduce
Steps to reproduce the behavior:
[email protected]:unikraft/app-helloworld.git
2. cd app-helloworold
3. kraft configure -p kvm -m x86_64
4. kraft build
Expected behavior
After building an application with the name
example
fromkraft.yaml
, the unikernel executable should have the nameexample_kvm-x86-64
even though the parent directory where this application has a different name.Screenshots
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: