Iago López Galeiras
Iago López Galeiras
It's actually [this function](https://github.com/coreos/rkt/blob/v1.7.0/stage1/init/init.go#L621) that fails [if it can't detect if it's running from a system service](https://github.com/coreos/rkt/blob/v1.7.0/stage1/init/init.go#L721). In this case, we can assume we're not running on a system service...
It seems there're more tests that use aci server: `TestRenderOnFetch`, `TestAuth*`...
Thanks for this! Now we need to fix the CI. As @alban says in https://github.com/rkt/rkt/issues/3790 there was a change in system that made rkt not work when systemd
> it doesn't make sense to enable *keep-unit* when we're not running in a systemd service Now that I look at the [commit that added this `allocate_scope` function](https://github.com/systemd/systemd/commit/cd2dfc6faea), maybe it...
They are two different failures, you often need to go further up to see the actual error. ### Job 1 (KVM) I assume this KVM build failure happens now because...
Cool! Hopefully we're getting close. For the KVM flavor, let's worry about it after we fix all the issues in the CoreOS flavor. Yes, we should fix those Job 2...
It seems systemd added an extra directory level in the cgroupv1 hierarchy (https://github.com/systemd/systemd/commit/720f0a2f3c928cc9379501a52146be9fbb4d9be2) whereas before they only had that extra directory in the cgroupv2 hierarchy. This breaks rkt's cgroup settings...
From what I understand, we added the flags `--mutable` and `--ipc` without implementing it in the fly stage1, this means the user would just get a warning when trying to...
I started writing a solution in [systemd/systemd#6763](https://github.com/systemd/systemd/pull/6763) but it needs a rework.
It seems this was addressed partially: `scripts/setup-data-dir.sh` was synced with `init/systemd/tmpfiles.d/rkt.conf` at the time. However, to close this we should check that they're still on sync, and address the bonus...