container create failed: sd-bus call: Cannot set property CPUQuotaPeriodUSec, or unknown propert about crun HOT 8 OPEN

I met the same issue, how to solve it?

Abandoning crun and embracing runc. Runc doesn't have this issue. Alternatively, upgrading systemd would require upgrading the operating system. However, I have chosen runc.

from crun.

The error from crun :

  if (UNLIKELY (sd_err < 0))
    {
      if (reset_failed_unit (bus, scope) == 0)
        {
          sd_bus_error_free (&error);
          if (reply)
            sd_bus_message_unref (reply);

          error = SD_BUS_ERROR_NULL;
          reply = NULL;

          sd_err = sd_bus_call (bus, m, 0, &error, &reply);
        }
      if (sd_err < 0)
        {
          ret = crun_make_error (err, sd_bus_error_get_errno (&error), "sd-bus call: %s", error.message ?: error.name);
          goto exit;
        }
    }

from crun.

 crun --version
crun version 1.8.3
commit: 59f2beb7efb0d35611d5818fd0311883676f6f7e
rundir: /run/user/0/crun
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL

from crun.

please update your version of systemd, crun doesn't not have the same check in place as runc for the systemd version

from crun.

please update your version of systemd, crun doesn't not have the same check in place as runc for the systemd version

The confusing part for me is that runc has a prompt for the systemd version, but it still executes successfully. On the other hand, crun does not have a corresponding prompt for the systemd version. Can crun use similar logic as runc?

from crun.

I met the same issue, how to solve it?

from crun.

The confusing part for me is that runc has a prompt for the systemd version, but it still executes successfully. On the other hand, crun does not have a corresponding prompt for the systemd version. Can crun use similar logic as runc?

if anyone cares enough to send a patch, we can consider that.

I met the same issue, how to solve it?

systemd 242 was released 5 years ago. What system are you using?

from crun.

In my case, we run debian10 mostly. Fortunately, buster-backports includes newer systemd so we can continue with crun.

ps. thanks for the excellent zombie reporting, we discovered a bad probe script from its output.

from crun.