Jan ☕🎼🎹☁️🏋️♂️<p>Been testing out the <a href="https://fedi.kcore.org/tags/virtiofs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>virtiofs</span></a> support now baked into <a href="https://fedi.kcore.org/tags/proxmoxVE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>proxmoxVE</span></a>. It works, had to do some <a href="https://fedi.kcore.org/tags/selinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>selinux</span></a> adjustments on <a href="https://fedi.kcore.org/tags/fedora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fedora</span></a> to allow my <a href="https://fedi.kcore.org/tags/podman" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>podman</span></a> containers to use the mountpoint. Added this policy</p><p>```<br>(allow container_t unlabeled_t ( dir ( read write )))<br>```</p><p>In raw speed it is definitely not a winner - <a href="https://fedi.kcore.org/tags/nfs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>nfs</span></a> is easily double the speed. But on this particular VM I don't need the speed - it is nice that this is all self-contained now, and I can actually remove NFS altogether.</p><p><a href="https://fedi.kcore.org/tags/proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>proxmox</span></a></p>