We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/etc
rootfs
The README states:
In this example, the populated root filesystem will look like this: rootfs/ ├── lib │ └── x86_64-linux-gnu │ └── libc.so.6 ├── lib64 │ └── ld-linux-x86-64.so.2 └── helloworld
In this example, the populated root filesystem will look like this:
rootfs/ ├── lib │ └── x86_64-linux-gnu │ └── libc.so.6 ├── lib64 │ └── ld-linux-x86-64.so.2 └── helloworld
Following the rest of the steps in the README results in this crash when running the helloworld example for the first two times:
[ 0.102110] ERR: [appelfloader] <conffile.c @ 92> /etc/resolv.conf: Failed to create: Permission denied (13) [ 0.104548] ERR: [libukboot] <boot.c @ 427> Init function at 0x11d420 returned error -13 [ 0.106414] CRIT: [libuk9p] <9pdev.c @ 118> Assertion failure: uk_list_empty(&fid_mgmt->fid_active_list)
After the two run, the rootfs has changed (the first run seems to create the resolv.conf file, the second the hosts file; both are empty):
resolv.conf
hosts
ls rootfs/etc . .. hosts resolv.conf
If the etc directory and the two files are present, it works from the start. Not sure if this is a Unikraft bug or an issue with the docs here.
etc
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The README states:
Following the rest of the steps in the README results in this crash when running the helloworld example for the first two times:
After the two run, the
rootfs
has changed (the first run seems to create theresolv.conf
file, the second thehosts
file; both are empty):If the
etc
directory and the two files are present, it works from the start. Not sure if this is a Unikraft bug or an issue with the docs here.The text was updated successfully, but these errors were encountered: