FFock

BTW, I did not add something to the `/etc/systemd/system/crio.service` but tried to change the original `NO_PROXY` setting by a version using CIDR addresses. Because normally, Rancher RKE has its means...

Having the proxy stuff fixed by sysbox would be great because I just setup a fresh cluster and did the above steps of my workaround except that I did not...

A short note about the current status: I was not able to get my workaround running again. The node and its sysbox setup are not proper anymore. I am not...

@rodnymolina I revisited this issue when preparing our next training environment and I hoped I could now use sysbox, but the situation got even worse. Besides this still unresolved proxy...

I tried to fix it with the code below (managed to get the global variable `DisableTlsCertificateVerification ` correctly set and derived from the `insecureSkipVerify ` in main. So that is...

With RKE2, K8S 1.25.9 and Ubuntu 22.04, the Longhorn volume mount with fsGroup pod security context works, however mounting a secret with fsGroup set, still mounts the secret with `nobody:nogroup`.

@rodnymolina, sure, I can provide the requested data. Can I sent it on a private channel?

We observed the same or similar bug when migrating several TB of Maven artifacts to a Gitea Maven repository. We now have many packages that cannot be deleted, because the...

To answer part of my question myself, the `allow-immutable-remounts=true` option can be activated by `vi /lib/systemd/system/sysbox-fs.service` edit the line with `ExecStart=/usr/bin/sysbox-fs` on the host to: ``` ExecStart=/usr/bin/sysbox-fs --allow-immutable-remounts=true ``` The...

When the container is started with `read-only` **and** sysbox-fs is started with `--allow-immutable-remounts=true` then I got an error on the remount of `/sys/fs/cgroup` fails with the following error (as noted...