Conversation
|
Arg can't get the node: https://github.com/docker/buildx/actions/runs/7611314658/job/20726595786#step:6:5366 Looking at the logs: I see k3s is up and running: Don't think the following errors are related: Maybe you have an idea @AkihiroSuda? |
Nested containers with cgroup v2 needs this # cgroup v2: enable nesting
if [ -f /sys/fs/cgroup/cgroup.controllers ]; then
# move the processes from the root group to the /init group,
# otherwise writing subtree_control fails with EBUSY.
# An error during moving non-existent process (i.e., "cat") is ignored.
mkdir -p /sys/fs/cgroup/init
xargs -rn1 < /sys/fs/cgroup/cgroup.procs > /sys/fs/cgroup/init/cgroup.procs || :
# enable controllers
sed -e 's/ / +/g' -e 's/^/+/' < /sys/fs/cgroup/cgroup.controllers \
> /sys/fs/cgroup/cgroup.subtree_control
fi |
Looks better now, thanks @AkihiroSuda! I'm looking at the tests failure https://github.com/crazy-max/buildx/actions/runs/7624605445/job/20767159528#step:6:54 Most likely linked to the local registry that can't be accessed from the node as it runs from the host. |
fefe715 to
a064d99
Compare
38780af to
2275c40
Compare
|
Can't use k3s 1.32 or 1.33: https://github.com/docker/buildx/actions/runs/15923094846/job/44914165242#step:7:10293 Is it a bug in k3s that generates a wrong containerd config? Edit: Ok seems it's because containerd shipped with docker is currently 1.7. |
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
Add integration tests for
kubernetesdriver.