FreeBSD: docs update and rootfs detection
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go
- Domain
- documentation, infrastructure
Research direction
Start with docs/tutorials/freebsd-workloads.md, which describes the init_path fallback and the arguments passed to the guest. Then find in the Go code where init_path is set from the container command, and check the docs against it. Done means the tutorial matches that behaviour, and the rootfs-detection question is answered with a measured cost and a recorded decision, with code added only if the cost is low.
Written by the indexing model from the issue text.
Description
The FreeBSD docs in urunc don't match how urunc boots FreeBSD guests.
Running without urunit (plain init)
- The docs say the kernel gets
init_path=/urunit:/sbin/urunit:/sbin/initand that images without urunit fall back to/sbin/init. In fact, urunc sets init_path to the first token of the container command, so a non-urunit entrypoint becomes init. The kernel's default init is used only when the command is empty. - When init isn't urunit, urunc passes nothing else to the guest: no arguments, env, uid/gid, working directory or network configuration. The docs should say so.
Moreover, urunc doesn't detect the rootfs filesystem. We should check if detection adds extra cost and if not, then we should add it.
- Dominant language
- Go
- Stars
- 306
- Forks
- 214
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 24
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from urunc-dev/urunc
-
Containers handed over to runc cannot be started, killed or deleted when urunc runs without --rootPossibly taken @Daksha1611 claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
urunc-dev/urunc#1127 · 3 comments ·
Maintainers usually reply within 1 day
-
urunc-deploy cleanup never labels the node, so the cleanup DaemonSet does not runPossibly taken @Sarthak-Shreshtha01 claimed this 3 days ago. Openbug K8s/Tools
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Rumprun guests receive &, < and > as \u0026, \u003c and \u003ePossibly taken @Sarthak-Shreshtha01 claimed this 9 days ago. Openbug Guests
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
urunc-dev/urunc#1074 · 4 comments ·
Maintainers usually reply within 1 day
-
Hooks run concurrently instead of in the listed orderMay be free again @anishmehta24 claimed this 15 days ago, and no pull request is open. OpenCore enhancement OCI
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
urunc-dev/urunc#1066 · 2 comments ·
Maintainers usually reply within 1 day
-
Flag to keep pulled images on local runs of e2ePossibly taken @slash-init claimed this 10 days ago. Opendev
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
urunc-dev/urunc#1057 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
plugins: symlinked plugin directories are skippedPossibly taken @lab1207 claimed this today. Openbug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
eugenioenko/ttt#1029 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Edwin-metcalf/MetCode#24 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
needs-operator
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
keyxmakerx/Chronicle#1654 ·
Maintainers usually reply within 1 day
-
area/security kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
agent-substrate/substrate#2935 ·
Maintainers usually reply within 1 day