Jan Pazdziora

@zeitue So you say `:rw` does not always work. Did you try the `--mount type=bind,src=/sys/fs/cgroup,dst=/sys/fs/cgroup,readonly,bind-recursive=writable` that @m3e-g suggested and does that work for you in all scenarios with docker 25?

@m3e-g To test how compatible that `--mount type=bind,src=/sys/fs/cgroup,dst=/sys/fs/cgroup,readonly,bind-recursive=writable` is, I tried it with docker 24.0.8 which is on the latest GitHub Actions Ubuntu 20.04 image. I got ``` invalid argument...

If you have `/sys/fs/cgroup/unified` on the host (the hybrid setup with v2 mounted there), can you try to use `-v /sys/fs/cgroup/unified:/sys/fs/cgroup:rw`? If you are doing a new installation, `--skip-mem-check` parameter...

This was now added to our GitHub Actions CI tests and to the README.

In `master`, I've now updated the K3s tests to use the `--ip-address`, and I've updated the README to prefer the `--ip-address` approach.

I've updated the README to document the approach in `master` via dd78e22eaedd07284d7640129878e7334156a4d6.

On related note, I'm also concerned by a double expansion attempts caused by ``` cmd = self.gen_cmd(args) cmd = self.sub_env_strings(cmd) self.display(cmd) if self.args.display: return if not self.args.quiet: self.check_args(cmd) if not...

I'm not sure what the expected behaviour and handling of dollars should be. I have atomic-1.13.1-1.el7.x86_64 and I see ``` # docker build -t issue-540 . Sending build context to...

Right, nothing as well: ``` # jezek="foobar" atomic run --opt1='$jezek' issue-540 docker run --rm issue-540 echo the value: the value: ```

Could you provide steps to reproduce the situation which currently leads to failure?