| *** ricolin_ is now known as ricolin | 16:26 | |
| *** ricolin_ is now known as ricolin | 17:32 | |
| kata-irc-bot2 | <efoster> Hey folks, I have a quick question. I'm on Kata 1.x, so this may a moot point once we're finished moving to 2.x. I noticed that Kata keeps a copy of the rootfs of every container under `/var/run/kata-containers/shared/sandboxes/$sandbox-id/mounts`. `/var/run` is a `tmpfs` on Flatcar, so we're running out of space there with some containers that have very large rootfs. Is there a way to move that location from `/var/run`? I | 17:35 |
|---|---|---|
| kata-irc-bot2 | <efoster> Hey folks, I have a quick question. I'm on Kata 1.x, so this may a moot point once we're finished moving to 2.x. I noticed that Kata keeps a copy of the rootfs of every container under `/var/run/kata-containers/shared/sandboxes/$sandbox-id/mounts`. `/var/run` is a `tmpfs` on Flatcar, so we're running out of space there with some containers that have very large rootfs. Is there a way to move that location from `/var/run`? I'm not | 17:35 |
| kata-irc-bot2 | seeing it in `configuration.toml`, but I may be missing something obvious. | 17:35 |
| kata-irc-bot2 | <fidencio> No, there's no option to change that, I'm afraid. | 17:39 |
| kata-irc-bot2 | <david_hay> Time for another dumb question (!) - I'm trying, perhaps unwisely, to add `containerd` to the pod sandbox / guest VM by adding it to `EXTRA_PKGS` via: - `EXTRA_PKGS="containerd" USE_DOCKER=true ./rootfs-builder/rootfs.sh -r ~/fedora_rootfs fedora` However, to start, the `containerd` service ( which runs via `systemctl` ) needs to find `overlay` and `br_netfilter` neither of which, by default, are available within the pod sandbox | 17:49 |
| kata-irc-bot2 | I'm considering using `KERNEL_MODULES_DIR` to include them, but am I barking up the wrong tree ? Is this a truly daft idea ? | 17:49 |
| kata-irc-bot2 | <efoster> Drat. We'll have to see what we can do. I guess maybe create a mountpoint at `/var/run/kata-containers` | 17:56 |
| kata-irc-bot2 | <efoster> I can do some homework as well, but do you know why Kata stores a copy of the rootfs there? I have someone asking me and I'm honestly not too sure myself | 18:20 |
| kata-irc-bot2 | <efoster> I assume it has something to do with virtio-fs | 18:20 |
| kata-irc-bot2 | <fidencio> ```root 269342 0.0 0.0 122804 4744 ? Sl Jun07 0:00 /usr/libexec/virtiofsd --fd=3 -o source=/run/kata-containers/shared/sandboxes/3d71ef4dcb7038bf5899e9b4b19a0a8125acfda88223e1b825b1e6d1dbfe4b9e/shared -o cache=auto --syslog -o no_posix_lock -f --thread-pool-size=1``` Yep, those are used by virtiofsd. | 18:41 |
| kata-irc-bot2 | <efoster> sweet, good to know! Hopefully there's not too much of a penalty from running those off of a regular disk. | 19:40 |
| kata-irc-bot | <fidencio> That's an important point, and I'd definitely ask Dave / Vivek about that. | 20:32 |
| kata-irc-bot | <eric.ernst> it isn’t a copy, but a bind mount, right? | 23:05 |
| kata-irc-bot | <eric.ernst> These shouldn’t be adding a lot of size, since they are just a mount of what’s already on the host from whatever snapshotter you are using. | 23:06 |
| kata-irc-bot | <eric.ernst> I’d have them take a look at the actual cost, size wise, of that path, versus elsewhere on the filesystem | 23:06 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!