| *** ebb has joined #kata-general | 00:08 | |
| *** pvdp66556 has quit IRC | 00:45 | |
| *** pvdp66556 has joined #kata-general | 00:48 | |
| *** tmhoang2 has joined #kata-general | 02:27 | |
| *** tmhoang has quit IRC | 02:27 | |
| *** tmhoang2 is now known as tmhoang | 02:27 | |
| *** bpradipt has joined #kata-general | 05:13 | |
| *** sameo has joined #kata-general | 05:18 | |
| *** sameo has quit IRC | 06:13 | |
| *** rha has joined #kata-general | 06:26 | |
| *** sgarzare has joined #kata-general | 06:57 | |
| *** sgarzare_ has joined #kata-general | 06:59 | |
| *** sgarzare has quit IRC | 07:02 | |
| *** sgarzare_ has quit IRC | 07:26 | |
| *** sgarzare has joined #kata-general | 07:41 | |
| *** sameo has joined #kata-general | 07:54 | |
| *** sgarzare has quit IRC | 09:26 | |
| *** sgarzare has joined #kata-general | 09:27 | |
| *** sgarzare has quit IRC | 10:14 | |
| *** sgarzare has joined #kata-general | 10:14 | |
| *** devimc has joined #kata-general | 12:10 | |
| *** sgarzare_ has joined #kata-general | 13:26 | |
| *** sgarzare has quit IRC | 13:29 | |
| *** pvdp66556 has quit IRC | 13:38 | |
| *** devimc has quit IRC | 14:08 | |
| *** devimc has joined #kata-general | 14:08 | |
| *** bpradipt has quit IRC | 14:18 | |
| *** sgarzare__ has joined #kata-general | 14:18 | |
| *** bpradipt has joined #kata-general | 14:18 | |
| *** sgarzare_ has quit IRC | 14:20 | |
| *** sameo has quit IRC | 15:06 | |
| *** sgarzare__ has quit IRC | 16:01 | |
| *** sameo has joined #kata-general | 17:00 | |
| *** bpradipt has quit IRC | 17:08 | |
| *** bpradipt has joined #kata-general | 17:09 | |
| *** pvdp66556 has joined #kata-general | 19:27 | |
| *** bpradipt has quit IRC | 19:33 | |
| *** sameo has quit IRC | 19:34 | |
| *** bpradipt has joined #kata-general | 19:38 | |
| *** bpradipt has quit IRC | 19:48 | |
| kata-irc-bot1 | <ralf> I am trying to run a Docker container that is rather I/O bound with the kata-containers runtime. I've managed to pass a raw LVM device into the container that I can manually mount as a filesystem *within the container* alright when I grant the container with additional ``SYS_ADMIN`` capabilities. However, I prefer this to happen automatically at container startup -- without granting the ``SYS_ADMIN`` permission. I have tried Docker's | 20:28 |
|---|---|---|
| kata-irc-bot1 | ``--mount`` option but end up with a 9p mount; which is a no-go performance wise. Is there any way to have the kata runtime mount the file system inside of the container namespace without going through 9p or virtio-fs? | 20:28 |
| kata-irc-bot1 | <ralf> I would like to avoid going down the virtio-fs route as we are also considering switching to Firecracker and Firecracker doesn't support virtio-fs yet (https://github.com/firecracker-microvm/firecracker/issues/1180) | 20:32 |
| *** devimc has quit IRC | 21:07 | |
| kata-irc-bot1 | <eric.ernst> Yeah, that makes sense to me. Just to clarify, you running from Docker CLI, or via a CRI runtime? | 23:09 |
| kata-irc-bot1 | <eric.ernst> Also, are you passing it as a volume, or as an actual device? | 23:10 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!