Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Error starting Nix daemon through Docker inside act #60

Open
Strum355 opened this issue Dec 7, 2023 · 8 comments
Open

Error starting Nix daemon through Docker inside act #60

Strum355 opened this issue Dec 7, 2023 · 8 comments

Comments

@Strum355
Copy link

Strum355 commented Dec 7, 2023 •
edited by Hoverbear
Loading

From discord, heres the output when running nix-installer-action via act (on the fully-featured image):

[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::download complete
| Detected `$ACT` environment, assuming this is a https://github.com/nektos/act created container, set `NOT_ACT=true` to override this. This will change the setting of the `init` to be compatible with `act`
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Execution environment: {%0A    "NIX_INSTALLER_NO_CONFIRM": "true",%0A    "NIX_INSTALLER_DIAGNOSTIC_ATTRIBUTION": "GH-c47505c2-696f-4673-90c7-c17aedf358eb",%0A    "NIX_INSTALLER_MODIFY_PROFILE": "true",%0A    "NIX_INSTALLER_DIAGNOSTIC_ENDPOINT": "https://install.determinate.systems/nix/diagnostic",%0A    "NIX_INSTALLER_INIT": "none",%0A    "NIX_INSTALLER_START_DAEMON": "true",%0A    "NIX_INSTALLER_EXTRA_CONF": "trusted-users = root root\n"%0A}
| [command]/tmp/0e573188-ff00-4f89-8af9-d52b236b2898 install linux
|  INFO Step: Create directory `/nix`
|  INFO Step: Provision Nix
|  INFO Step: Create build users (UID 30000-30032) and group (GID 30000)
|  INFO Step: Configure Nix
|  INFO Step: Create directory `/etc/tmpfiles.d`
|  INFO Step: Leave the Nix daemon unconfigured
|  INFO Step: Remove directory `/nix/temp-install-dir`
|  WARN SelfTest([ShellFailed { shell: Sh, command: "\"sh\" \"-lc\" \"nix build --no-link --expr \\'derivation { name = \\\"self-test-sh-1701955359511\\\"; system = \\\"x86_64-linux\\\"; builder = \\\"/bin/sh\\\"; args = [\\\"-c\\\" \\\"echo hello > \\\\$out\\\"]; }\\'\"", output: Output { status: ExitStatus(unix_wait_status(512)), stdout: "", stderr: "sh: 10: .: cannot open /etc/skel/.cargo/env: No such file\n" } }])
| Nix was installed successfully!
| To get started using Nix, open a new shell or run `. /nix/var/nix/profiles/default/etc/profile.d/nix-daemon.sh`
| 
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❓  ::endgroup::
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❓  ::group::Configuring the Docker shim as the Nix Daemon's process supervisor
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Loading image: determinate-nix-shim:latest...
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Loaded image: determinate-nix-shim:latest
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Starting the Nix daemon through Docker...
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::07b80d704386e4f1b51c620ae47f21f2b165f49450c37c053b82dae2d663290f
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/nix/var/nix/profiles/default/bin/nix-daemon": stat /nix/var/nix/profiles/default/bin/nix-daemon: no such file or directory: unknown.
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❗  ::error::Error: The process '/usr/bin/docker' failed with exit code 127
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❌  Failure - Main DeterminateSystems/nix-installer-action@main
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ⚙  ::set-env:: DETERMINATE_NIX_KVM=0
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ⚙  ::add-path:: /nix/var/nix/profiles/default/bin
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ⚙  ::add-path:: /home/runner/.nix-profile/bin
[nix_p4-fusion/Build p4-fusion x86_64-linux  ] exitcode '1': failure

Local machine is x86_64-linux NixOS. Issue happened on both v8 and v9 pin, and both rootless and rootful docker
@colemickens
Copy link
Member

| WARN SelfTest([ShellFailed { shell: Sh, command: "\"sh\" \"-lc\" \"nix build --no-link --expr \\'derivation { name = \\\"self-test-sh-1701955359511\\\"; system = \\\"x86_64-linux\\\"; builder = \\\"/bin/sh\\\"; args = [\\\"-c\\\" \\\"echo hello > \\\\$out\\\"]; }\\'\"", output: Output { status: ExitStatus(unix_wait_status(512)), stdout: "", stderr: "sh: 10: .: cannot open /etc/skel/.cargo/env: No such file\n" } }])

hm

@cole-h
Copy link
Member

cole-h commented Dec 15, 2023

Just to be sure: this doesn't happen on v7, but it does happen on v8?

Could you show the error message for v8's failure (it won't be the same, because v9 introduced the Docker shim, whereas v8 only introduced kvm support)?

@Hoverbear
Copy link
Contributor

This appears similar to #63

@Strum355
Copy link
Author

Strum355 commented Jan 9, 2024

Just to be sure: this doesn't happen on v7, but it does happen on v8?

Could you show the error message for v8's failure (it won't be the same, because v9 introduced the Docker shim, whereas v8 only introduced kvm support)?

Testing again, I can only reproduce this on v9, I cant reproduce it on v7 or v8

@Hoverbear
Copy link
Contributor

I believe this should be fixed on the main branch, could you give it a shot?

@Strum355
Copy link
Author

I believe this should be fixed on the main branch, could you give it a shot?

Doesnt appear to work

[nix_p4-fusion/Build p4-fusion x86_64-linux  ] 🚀  Start image=catthehacker/ubuntu:full-latest
INFO[0029] Parallel tasks (0) below minimum, setting to 1 
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   🐳  docker pull image=catthehacker/ubuntu:full-latest platform= username= forcePull=true
[nix_p4-fusion/Build p4-fusion x86_64-linux  ] using DockerAuthConfig authentication for docker pull
INFO[0031] Parallel tasks (0) below minimum, setting to 1 
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   🐳  docker create image=catthehacker/ubuntu:full-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host"
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   🐳  docker run image=catthehacker/ubuntu:full-latest platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] network="host"
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ☁  git clone 'https://github.com/DeterminateSystems/nix-installer-action' # ref=main
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ☁  git clone 'https://github.com/DeterminateSystems/magic-nix-cache-action' # ref=main
[nix_p4-fusion/Build p4-fusion x86_64-linux  ] ⭐ Run Main actions/checkout@v4
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   🐳  docker cp src=/home/noah/Sourcegraph/p4-fusion/. dst=/home/noah/Sourcegraph/p4-fusion
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ✅  Success - Main actions/checkout@v4
[nix_p4-fusion/Build p4-fusion x86_64-linux  ] ⭐ Run Main DeterminateSystems/nix-installer-action@main
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   🐳  docker cp src=/home/noah/.cache/act/DeterminateSystems-nix-installer-action@main/ dst=/var/run/act/actions/DeterminateSystems-nix-installer-action@main/
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   🐳  docker exec cmd=[node /var/run/act/actions/DeterminateSystems-nix-installer-action@main/dist/index.js] user= workdir=
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Linux detected without systemd, testing for Docker with `docker info` as an alternative daemon supervisor.
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Client: Docker Engine - Community
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug:: Version:    24.0.7%0A Context:    default%0A Debug Mode: false%0A Plugins:%0A  buildx: Docker Buildx (Docker Inc.)%0A    Version:  v0.11.2%0A    Path:     /usr/libexec/docker/cli-plugins/docker-buildx%0A  compose: Docker Compose (Docker Inc.)%0A    Version:  v2.23.3%0A    Path:     /usr/libexec/docker/cli-plugins/docker-compose%0A%0AServer:%0A Containers: 12%0A  Running: 2%0A  Paused: 0%0A  Stopped: 10%0A Images: 165%0A Server Version: 24.0.5%0A Storage Driver: overlay2%0A  Backing Filesystem: zfs%0A  Supports d_type: true%0A  Using metacopy: false%0A  Native Overlay Diff: true%0A  userxattr: false%0A Logging Driver: journald%0A Cgroup Driver: systemd%0A Cgroup Version: 2%0A Plugins:%0A  Volume: local%0A  Network: bridge host ipvlan macvlan null overlay%0A  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog%0A Swarm: inactive%0A Runtimes: io.containerd.runc.v2 runc%0A Default Runtime: runc%0A Init Binary: docker-init%0A containerd version: v1.7.11%0A runc version: %0A init version: %0A Security Options:%0A  seccomp%0A   Profile: builtin%0A  cgroupns%0A Kernel Version: 6.1.71%0A Operating System: NixOS 24.05 (Uakari)%0A OSType: linux%0A Architecture: x86_64%0A CPUs: 12%0A Total Memory: 31.3GiB%0A Name: noah-nixos-desktop%0A ID: ea1882dd-2692-41e7-85be-99391ae0c8ee%0A Docker Root Dir: /var/lib/docker%0A Debug Mode: false%0A Experimental: false%0A Insecure Registries:%0A  127.0.0.0/8%0A Live Restore Enabled: true
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Did not detect a container ID, bailing on docker.sock detection
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❓  ::group::Enabling the Docker shim for running Nix on Linux in CI without Systemd.
| Changing init from 'null' to 'none'
| Changing planner from 'null' to 'linux'
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❓  ::endgroup::
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❓  ::group::Configuring KVM
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Failed to send reload request: No such file or directory
| [command]/usr/bin/rm -f /etc/udev/rules.d/99-determinate-nix-installer-kvm.rules
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❓  ::endgroup::
| KVM is not available.
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❓  ::group::Installing Nix
| Fetching binary from https://install.determinate.systems/nix/nix-installer-x86_64-linux?ci=github&correlation=GH-b2020bb4-f44f-4c9f-9d00-5c8dacfc2eac
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Downloading https://install.determinate.systems/nix/nix-installer-x86_64-linux?ci=github&correlation=GH-b2020bb4-f44f-4c9f-9d00-5c8dacfc2eac
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Destination /tmp/2640c724-300e-484e-9a68-860be427a554
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::download complete
| Detected `$ACT` environment, assuming this is a https://github.com/nektos/act created container, set `NOT_ACT=true` to override this. This will change the setting of the `init` to be compatible with `act`
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Execution environment: {%0A    "NIX_INSTALLER_NO_CONFIRM": "true",%0A    "NIX_INSTALLER_DIAGNOSTIC_ATTRIBUTION": "GH-b2020bb4-f44f-4c9f-9d00-5c8dacfc2eac",%0A    "NIX_INSTALLER_MODIFY_PROFILE": "true",%0A    "NIX_INSTALLER_DIAGNOSTIC_ENDPOINT": "https://install.determinate.systems/nix/diagnostic",%0A    "NIX_INSTALLER_INIT": "none",%0A    "NIX_INSTALLER_START_DAEMON": "true",%0A    "NIX_INSTALLER_EXTRA_CONF": "trusted-users = root root\n"%0A}
| [command]/tmp/2640c724-300e-484e-9a68-860be427a554 install linux
|  INFO Step: Create directory `/nix`
|  INFO Step: Provision Nix
|  INFO Step: Create build users (UID 30001-30032) and group (GID 30000)
|  INFO Step: Configure Nix
|  INFO Step: Create directory `/etc/tmpfiles.d`
|  INFO Step: Leave the Nix daemon unconfigured
|  INFO Step: Remove directory `/nix/temp-install-dir`
|  WARN SelfTest([ShellFailed { shell: Sh, command: "\"sh\" \"-lc\" \"nix build --no-link --expr \\'derivation { name = \\\"self-test-sh-1705011073440\\\"; system = \\\"x86_64-linux\\\"; builder = \\\"/bin/sh\\\"; args = [\\\"-c\\\" \\\"echo hello > \\\\$out\\\"]; }\\'\"", output: Output { status: ExitStatus(unix_wait_status(512)), stdout: "", stderr: "sh: 10: .: cannot open /etc/skel/.cargo/env: No such file\n" } }])
| Nix was installed successfully!
| To get started using Nix, open a new shell or run `. /nix/var/nix/profiles/default/etc/profile.d/nix-daemon.sh`
| 
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❓  ::endgroup::
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❓  ::group::Configuring the Docker shim as the Nix Daemon's process supervisor
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Loading image: determinate-nix-shim:latest...
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Loaded image: determinate-nix-shim:latest
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Starting the Nix daemon through Docker...
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::a4202b099a27734c51f6c8b76f01c3e8866dec51f864a18172462d3383192f76
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/nix/var/nix/profiles/default/bin/nix-daemon": stat /nix/var/nix/profiles/default/bin/nix-daemon: no such file or directory: unknown.
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❗  ::error::Error: The process '/usr/bin/docker' failed with exit code 127
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❌  Failure - Main DeterminateSystems/nix-installer-action@main
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ⚙  ::set-env:: DETERMINATE_NIX_KVM=0
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ⚙  ::add-path:: /nix/var/nix/profiles/default/bin
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ⚙  ::add-path:: /home/runner/.nix-profile/bin
[nix_p4-fusion/Build p4-fusion x86_64-linux  ] exitcode '1': failure
[nix_p4-fusion/Build p4-fusion x86_64-linux  ] ⭐ Run Post DeterminateSystems/nix-installer-action@main
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   🐳  docker exec cmd=[node /var/run/act/actions/DeterminateSystems-nix-installer-action@main/dist/index.js] user= workdir=
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Linux detected without systemd, testing for Docker with `docker info` as an alternative daemon supervisor.
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Client: Docker Engine - Community%0A Version:    24.0.7%0A Context:    default%0A Debug Mode: false%0A Plugins:%0A  buildx: Docker Buildx (Docker Inc.)%0A    Version:  v0.11.2%0A    Path:     /usr/libexec/docker/cli-plugins/docker-buildx%0A  compose: Docker Compose (Docker Inc.)%0A    Version:  v2.23.3%0A    Path:     /usr/libexec/docker/cli-plugins/docker-compose%0A%0AServer:%0A Containers: 13%0A  Running: 2%0A  Paused: 0%0A  Stopped: 11%0A Images: 165%0A Server Version: 24.0.5%0A Storage Driver: overlay2%0A  Backing Filesystem: zfs%0A  Supports d_type: true%0A  Using metacopy: false
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::  Native Overlay Diff: true%0A  userxattr: false%0A Logging Driver: journald%0A Cgroup Driver: systemd%0A Cgroup Version: 2%0A Plugins:%0A  Volume: local%0A  Network: bridge host ipvlan macvlan null overlay%0A  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog%0A Swarm: inactive%0A Runtimes: io.containerd.runc.v2 runc%0A Default Runtime: runc%0A Init Binary: docker-init%0A containerd version: v1.7.11%0A runc version: %0A init version: %0A Security Options:%0A  seccomp%0A   Profile: builtin%0A  cgroupns%0A Kernel Version: 6.1.71%0A Operating System: NixOS 24.05 (Uakari)%0A OSType: linux%0A Architecture: x86_64%0A CPUs: 12%0A Total Memory: 31.3GiB%0A Name: noah-nixos-desktop%0A ID: ea1882dd-2692-41e7-85be-99391ae0c8ee%0A Docker Root Dir: /var/lib/docker%0A Debug Mode: false%0A Experimental: false%0A Insecure Registries:%0A  127.0.0.0/8%0A Live Restore Enabled: true
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   💬  ::debug::Did not detect a container ID, bailing on docker.sock detection
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❓  ::group::Enabling the Docker shim for running Nix on Linux in CI without Systemd.
| Changing init from 'null' to 'none'
| Changing planner from 'null' to 'linux'
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ❓  ::endgroup::
| Added `/nix/var/nix/profiles/default/bin` and `/root/.nix-profile/bin` to `$GITHUB_PATH`
| Nix was already installed, using existing install
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ✅  Success - Post DeterminateSystems/nix-installer-action@main
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ⚙  ::add-path:: /nix/var/nix/profiles/default/bin
[nix_p4-fusion/Build p4-fusion x86_64-linux  ]   ⚙  ::add-path:: /root/.nix-profile/bin
[nix_p4-fusion/Build p4-fusion x86_64-linux  ] 🏁  Job failed

@Hoverbear
Copy link
Contributor

I wonder if your Docker works differently than the one I tested on...

Could I ask you to do docker run -ti --rm ubuntu and show me cat /proc/self/cgroup?

Here's mine:

❯ docker run -ti --rm ubuntu
root@ae953ab81323:/# cat /proc/self/cgroup
15:name=systemd:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
14:misc:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
13:rdma:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
12:pids:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
11:hugetlb:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
10:net_prio:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
9:perf_event:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
8:net_cls:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
7:freezer:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
6:devices:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
5:memory:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
4:blkio:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
3:cpuacct:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
2:cpu:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
1:cpuset:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
0::/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711

@Strum355
Copy link
Author

Strum355 commented Jun 4, 2024

I wonder if your Docker works differently than the one I tested on...

Could I ask you to do docker run -ti --rm ubuntu and show me cat /proc/self/cgroup?

Here's mine:

❯ docker run -ti --rm ubuntu
root@ae953ab81323:/# cat /proc/self/cgroup
15:name=systemd:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
14:misc:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
13:rdma:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
12:pids:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
11:hugetlb:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
10:net_prio:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
9:perf_event:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
8:net_cls:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
7:freezer:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
6:devices:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
5:memory:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
4:blkio:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
3:cpuacct:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
2:cpu:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
1:cpuset:/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711
0::/docker/ae953ab81323d965e6b8177c0fbc0d01aa565f5fb69ff8579e57e988fdfea711

Sorry I completely forgot to get back to this 😮‍💨 Hoping this output makes sense for the issue (my system has gone through many updates since january)

$ cat /proc/self/cgroup
0::/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Hoverbear @colemickens @Strum355 @cole-h