skyper

It only happens if ntp is started via 'systemctl' (which is the default). It works fine when started directly from the command line. It appears that the problem is the...

hmm. There is a reason for this: gsocket should be the source only. IT's a development repository. Binaries are not for developers but for users. So it makes sense to...

thank you for the contribution. You are correct. At the moment it assumes to restart the file transfer. The user is (kindly) asked to remove existing files beforehand. I'll add...

I created a band new t2.small AWS instance. ```console # grep VERSION= /etc/os-release VERSION="22.04.2 LTS (Jammy Jellyfish)" # uname -r 5.15.0-1031-aws # docker --version Docker version 23.0.6, build ef23cbc #...

```console # docker run --rm --runtime=sysbox-runc alpine sh -c "mount | grep overlay" overlay on / type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/HGUDI5PFBMUX3O4APPGLCSC57R:/var/lib/docker/overlay2/l/QZUK4YM5VAVLOAYE5OAKAO6NTV,upperdir=/var/lib/sysbox/rootfs/b0e9a7049fddcd2076dd2a88a1999c5176ed750e368ae4a0024d4499e744b5f6/overlay2/diff,workdir=/var/lib/sysbox/rootfs/b0e9a7049fddcd2076dd2a88a1999c5176ed750e368ae4a0024d4499e744b5f6/overlay2/work,metacopy=on) /dev/loop5 on /var/lib/containerd/io.containerd.snapshotter.v1.overlayfs type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,prjquota) ``` I'll upgrade to 5.19...

Just to confirm that your suggestion to upgrade to 5.19 works. Thanks for the great work. ```console # uname -mrs Linux 5.19.17-051917-generic x86_64 # docker run --rm --runtime=sysbox-runc alpine sh...

@rodnymolina shiftfs is loaded. No luck. ```console # lsmod | grep shiftfs shiftfs 28672 0 # uname -r 5.4.0-146-generic # docker run --rm --runtime=sysbox-runc --net sf-guest alpine docker: Error response...

Hi, versions and mount points: ```console # grep VERSION= /etc/os-release VERSION="20.04.4 LTS (Focal Fossa)" # uname -r 5.4.0-146-generic # lsmod | grep shiftfs shiftfs 28672 0 # ls -ald /var/lib/docker...

special consideration is needed so that the container can't get around the container's cgroup restrictions (cpu accounting etc) if the host's /dev/kvm is *directly* exposed to the container, not?

this has now been done. thank you for your suggestions and explanations.