Robert Hensing

Failed to create /init.scope control group: Read-only file system

5

To reproduce 1. start a systemd-based container on NixOS 21.05 2. observe the error message in the log ``` Failed to create /init.scope control group: Read-only file system Failed to...

Try rootless podman networks

2

https://github.com/NixOS/nixpkgs/pull/125598#issuecomment-864099902, specifically https://github.com/containers/podman/issues/9169 Possible issue https://github.com/containers/podman/issues/10672 (not sure if "internal" network is used) Ideally it just works and all that's needed is a one or two lines of docs.

Error: [...] is in state configured: container state improper

1

This happens with podman sometimes. I experience it after restarting my system. For example on `arion up -d`: ``` ERROR: for hercules_web_1 can only stop created or running containers. 4b3cabe1adea3a93279c36d4f6e079351fcdc1a72d7a473c968ab78e61f67bde...

Cache misses

1

The NixOS configuration includes the no-x-libs overlay by default, which is unexpected and causes cache misses, depending on which `pkgs` you're using (from arion or from nixos) See https://github.com/tfc/module-recompiles-qemu/issues/1

Add test cases: - docker-compose json with all fields set - assertion at composition level - assertion at service level - same for s/assertion/warning

- Invoke `docker stack` - Update docs - Clarify differences between it and docker-compose

- The docker compose v3 format is on a new url. - We only have `master` on antora

Entrypoint is an important one. Most if not all others should be added. Fields with a `service`-equivalent should be supported in for `useHostStore`.