Don't use docker shim if only using a mounted docker.sock instead of docker-in-docker #67

Merged
Hoverbear merged 1 commit from hoverbear/fh-161-after-running-in-act-hosts-nix-daemon-is-unusable into main 2024-01-11 15:55:46 +00:00
Hoverbear commented 2024-01-10 19:45:42 +00:00 (Migrated from github.com)
Description

I believe this fixes https://github.com/DeterminateSystems/nix-installer-action/issues/65.

Checklist
  • Tested changes against a test repository
  • Added or updated relevant documentation (leave unchecked if not applicable)
  • (If this PR is for a release) Updated README to point to the new tag (leave unchecked if not applicable)
##### Description I believe this fixes https://github.com/DeterminateSystems/nix-installer-action/issues/65. ##### Checklist - [ ] Tested changes against a test repository - [ ] Added or updated relevant documentation (leave unchecked if not applicable) - [ ] (If this PR is for a release) Updated README to point to the new tag (leave unchecked if not applicable)
cole-h (Migrated from github.com) approved these changes 2024-01-10 22:52:11 +00:00
cole-h (Migrated from github.com) left a comment

I think this looks sound overall, but I'm not extremely familiar with docker or cgroups and the like, so take this approval with a grain of salt...

I think this looks sound overall, but I'm not extremely familiar with docker or cgroups and the like, so take this approval with a grain of salt...
@ -185,0 +240,4 @@
stdout: (data: Buffer) => {
stdout_buffer += data.toString("utf-8");
},
stderr: (data: Buffer) => {
cole-h (Migrated from github.com) commented 2024-01-10 22:52:08 +00:00

Would it be worth it to check every cgroup line to see if there is /docker/ in it, or if it's in an earlier cgroup, is that a weird configuration we wouldn't want to support anyways?

Would it be worth it to check _every_ cgroup line to see if there is `/docker/` in it, or if it's in an earlier cgroup, is that a weird configuration we wouldn't want to support anyways?
colemickens (Migrated from github.com) approved these changes 2024-01-11 15:28:26 +00:00
colemickens (Migrated from github.com) left a comment

Also no cgroup expert, but the code matches what was described, and the description I was given sounded convincing for detecting this scenario and avoiding it.

Also no cgroup expert, but the code matches what was described, and the description I was given sounded convincing for detecting this scenario and avoiding it.
Hoverbear (Migrated from github.com) reviewed 2024-01-11 15:54:27 +00:00
@ -185,0 +240,4 @@
stdout: (data: Buffer) => {
stdout_buffer += data.toString("utf-8");
},
stderr: (data: Buffer) => {
Hoverbear (Migrated from github.com) commented 2024-01-11 15:54:27 +00:00

I don't have access to every system and setup, only a few, but I think in this case we're only looking for the 0:: prefixed line which is always last.

I don't have access to every system and setup, only a few, but I think in this case we're only looking for the `0::` prefixed line which is always last.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/lix-install-action#67
No description provided.