search

hackerschoice / segfault

358 stars 41 forks source link

support docker #4

Open SkyperTHC opened 2 years ago

SkyperTHC commented 2 years ago

That's a big one as we are already inside docker and cant use DinD.

Needs a micro Linux VM (executed by qemu because there is no /dev/kvm). Then run Docker inside MicroVM (similar to what MacOS does).

None of these works for us but some ideas can be taken from:

DeadPackets commented 2 years ago

https://github.com/gotoz/runq seems to be the solution to this.

Edit: I noticed that its not pure QEMU, and needs KVM. Should give it a shot though, still.

arizvisa commented 2 years ago

maybe not use docker (or consider podman in docker):

$ id -u;podman run --security-opt label=disable --user podman --device /dev/fuse quay.io/podman/stable podman run --security-opt label=disable --user podman quay.io/podman/stable /bin/sh -c id
1000
time="2022-10-24T18:19:01Z" level=warning msg="\"/\" is not a shared mount, this could cause issues or missing mounts with rootless containers"
Trying to pull quay.io/podman/stable:latest...
Getting image source signatures
Copying blob sha256:f9520f568cbb384e9989bb3ce22ce688611196d1b4a6c5f5a4496db8e7e53117
Copying blob sha256:83a256ce2f059a8daad1ecdee00d87efff5590ed37a71191286b8962ef9a76ec
Copying blob sha256:62946078034b7fe37984579d9b82ccf20cc98ffcd6517cf79ffad18e06fe2b23
Copying blob sha256:9c4f37a1b24fe582eeaf37cfeb52dbf4077fcdc30229106d9eccf599a2f57e6c
Copying blob sha256:a7e20175426fd62d0ed6e65a439d83d20ecd7997df642ec9b6535696d50c3c70
Copying blob sha256:e7b7ab4e6f53d19448d41eadfe0b2850d2cbb73890ad517f6b91be49ff0b229a
Copying blob sha256:71d521682f94d3f94eacdab55118e700959ae6599011f9e96dd04bb57befd21f
Copying blob sha256:1a2a5613248ca729a286ce7be5de9e6b7bc251a465dbcfebfe0132031cd5465d
Copying config sha256:2c99440451ec72cc6dcf9172125e45d12b15f0f7b1f8dc02c5953f364768a014
Writing manifest to image destination
Storing signatures
uid=1000(podman) gid=1000(podman) groups=1000(podman)