helm / helm/kind-action

Support KIND running inside container

Open
#30 10 comments 10 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
382
Forks
98
Avg merge
20h 41m
Merged PRs (30d)
1

Description

Currently we have KIND running in our Kubernetes CI, where KIND runs inside of a pod/container, which requires the following mounts with the node:
```
volumeMounts:
- mountPath: /lib/modules
name: modules
readOnly: true
- mountPath: /sys/fs/cgroup
name: cgroup
- name: dind-storage
mountPath: /var/lib/docker
securityContext:
privileged: true
imagePullPolicy: Always
volumes:
- name: modules
hostPath:
path: /lib/modules
type: Directory
- name: cgroup
hostPath:
path: /sys/fs/cgroup
type: Directory
- name: dind-storage
emptyDir: {}
```

When running a KIND docker action inside a KIND enabled container (which works on kubernetes) such as:
```
...
runs-on: ubuntu-18.04
container: repo/container:tag
...
```
It seems to work when running it locally using `act` (https://github.com/nektos/act), but when running it on the github Actions worker, I get the error `Error: Kubernetes cluster unreachable: Get https://127.0.0.1:34221/version?timeout=32s: dial tcp 127.0.0.1:34221: connect: connection refused`.

The KIND cluster does seem to get correctly created, but the issue seems to mainly be that the cluster is not reachable. Is this an issue that you have come across before?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.