
<p>In a standard container setup, the container shares the network namespace with</p><p>its host environment, meaning localhost inside the container refers to the same</p><p>loopback interface as the host's network namespace. Many CNI plugins and</p><p>container networking services rely on this assumption. For instance, Docker</p><p>sets up an internal DNS server listening on localhost within each container's</p><p>network namespace and configures `/etc/resolv.conf` accordingly. Similarly,</p><p>service meshes (e.g., Istio, Linkerd) inject sidecar proxies that listen on</p><p>localhost, and certain CNI plugins expose health checks or metrics endpoints on</p><p>the loopback interface.</p><p><br></p><p> In urunc, however, workloads execute inside a sandboxed environment</p><p>with its own isolated network stack. As a result,</p><p>localhost inside the sandbox does not refer to the host's network namespace</p><p>loopback interface but to the sandbox's own. This breaks any service that</p><p>relies on localhost-based communication between the container and host-level</p><p>components.</p><p><br></p><p>This project aims to investigate and implement mechanisms to bridge localhost</p><p>communication between the host network namespace and the sandbox. The mentee</p><p>will survey the landscape of CNI plugins and networking services that rely on</p><p>localhost, categorize the different communication patterns, and design a</p><p>solution that restores compatibility while preserving the</p><p>isolation guarantees that urunc provides.</p><p><br></p><p>- Expected Outcome:</p><p> - A survey and categorization of CNI plugins and networking services that</p><p> rely on localhost communication, documenting the specific patterns and</p><p> assumptions each makes.</p><p> - A design proposal of one or more mechanisms to bridge localhost traffic</p><p> between the host network namespace and the sandbox.</p><p> - Implementation of the proposed solution in urunc, with DNS resolution as</p><p> the primary use case.</p><p> - Evaluation of the new mechanism.</p><p><br></p>
No project history available for this organization.
Counts are based on projects listed in the Contribo catalog.
Showing 5 of 6 projects. Click any project card for scope, mentors, and proposal studio.
In order to pass sandbox-specific configuration, such as the guest type, monitor type, rootfs information and others, `urunc` relies on a set of [custom OCI annotations](https://urunc.io/package/#annotations). However, these annotations are missing from the container's configuration in non-Kubernetes-deployments. To work around this issue, a `urunc.json` file containing the same information is currently injected into the container’s root filesystem. This works aims to investigate the OCI image build and runtime flow to understand where and why these custom annotations are dropped or ignored in non-Kubernetes setups. - Expected Outcome: - A clear summary of the investigation, including where and why the custom annotations are lost. - A proposed solution enabling `urunc` to correctly consume its custom OCI annotations. - Alternatively, the design and implementation of a cleaner mechanism than injecting a file into the container’s root filesystem.
When `urunc` is used together with a block-based snapshotter, it can take advantage of block-device backed container root filesystem and pass it directly to the sandbox as a disk image. This approach avoids filesystem conversion and enables efficient access to the container root filesystem. However, in order to spawn the sandbox, urunc requires access to the guest kernel and the initrd (if present). Since these files are part of the container rootfs, `urunc` must first extract and store them elsewhere before attaching the block-based root filesystem to the sandbox. As a result, this process introduces unnecessary file copies and additional I/O overhead. A more efficient approach is to leverage read-only (view) snapshots. Instead of copying files, `urunc` could request a read-only snapshot of the container root filesystem and mount it separately. The kernel binary and other required artifacts could then be read directly from this snapshot without modifying or duplicating data. Since view snapshots simply redirect read requests to the underlying snapshot layers, this approach is expected to introduce little to no additional storage overhead while simplifying the runtime flow. - Expected Outcome: - A document explaining block-based snapshots in containerd, along with the respective APIs to snapshot creation and management. - An implementation in `urunc` that requests and mounts a read-only snapshot of the container root filesystem. - Evaluation of performance
GitHub Actions provides detailed views of CI workflows at the repository level, but it can be difficult for maintainers to quickly track the overall status of recurring workflows, such as nightly tests, over time. Important information, like historical failures or trends, often requires manual inspection of individual workflow runs. This work aims to improve CI observability for `urunc` by creating a centralized dashboard that presents an aggregated view of its nightly (and other CI) test workflows. The dashboard will provide maintainers with a clear overview of recent runs, success and failure states, and relevant metadata in a single place. In addition to visualization, this work includes the design and implementation of a notification mechanism that alerts maintainers when tests fail. This will help ensure that regressions are noticed quickly and addressed in a timely manner, improving overall project reliability. - Expected Outcome: - Design and implementation of a dashboard summarizing nightly (and CI) test results. - Clear visualization of workflow status and execution history. - Implementation of a notification system for nightly test failures. - Documentation describing the dashboard, notification setup, and maintenance.
<p>Currently, urunc launches sandbox monitors, such as Firecracker and QEMU</p><p>through command-line invocations. This approach offers limited control over the</p><p>sandbox lifecycle once the process is started. On the other hand, most</p><p>monitors expose remote management interfaces, typically through a socket-based</p><p>API.</p><p><br></p><p>These interfaces provide access to the same operations currently performed via</p><p>CLI, but also enable further control over the sandbox lifecycle. In particular,</p><p>they allow more fine-grained lifecycle management of the sandbox, including</p><p>querying and monitoring its state, performing device hotplug and unplug</p><p>operations and interacting with the guest.</p><p><br></p><p>This project aims to extend urunc's sandbox integration layer to support remote</p><p>management interfaces and to explore each monitor's capabilities in order to</p><p>extend the functionalities of urunc sandboxed containers.</p><p><br></p><p>Expected Outcome:</p><p> - A design document describing the updated architecture and workflow for</p><p> spawning and managing sandbox monitors in urunc.</p><p> - Implementation of the necessary changes in urunc to manage sandbox monitors</p><p> through their respective APIs.</p>
<p>According to urunc's execution model, the application executes inside a</p><p>VM-based or software-based sandbox. While this model strengthens isolation</p><p>boundaries, it can introduce performance overhead and additional resource</p><p>consumption compared to standard containers. Over the past years, evaluations</p><p>of urunc have focused primarily on spawn time and container density and less</p><p>on other aspects, such as CPU and memory usage, storage overhead I/O</p><p>performance and network latency.</p><p><br></p><p>As a result, it is necessary to conduct a thorough performance evaluation of</p><p>urunc across multiple metrics. The evaluation should span across</p><p>microbenchmarks, macrobenchmarks, and representative real-world workloads.</p><p>Apart from the evaluation itself, it is also important to create a reproducible</p><p>benchmarking suite, with all scripts, tools and documentation, so that anyone</p><p>can extend and reproduce the experiments across different environments and</p><p>versions.</p><p><br></p><p>- Expected Outcome:</p><p> - A comprehensive evaluation report covering startup latency, CPU and memory</p><p> consumption, storage overhead, I/O throughput, and network performance</p><p> across multiple sandboxes (monitor / guest combinations).</p><p> - A reproducible evaluation suite, including all scripts, tools,</p><p> configurations and documentation required to repeat and extend the</p><p> benchmarks.</p><p> - A blogpost summarizing the methodology and the findings of the evaluation.</p><p><br></p>