2 ms·

I wonder how this tool handles performing the docker build itself. It looks like it runs a controller inside the cluster, but by default apps running inside kub

by dlor 9y ago

I wonder how this tool handles performing the docker build itself. It looks like it runs a controller inside the cluster, but by default apps running inside kubernetes don't get access to the docker daemon. There are a few existing workarounds, but none of them are terribly appealing. See this longstanding issue for some more context: https://github.com/kubernetes/kubernetes/issues/1806 https://github.com/kubernetes/kubernetes/issues/1806

tirumaraiselvan 9y ago
Docker sock is being mounted from the host [1]. This could be a concern if you are running multi-tenant apps etc. One (slightly hacky) workaround is to have a Persistent Volume mount the hostPath and restrict hostPath mounting in the pod through PSPs. [1] https://github.com/hasura/gitkube/blob/7d0e7f25b811d48089b788593fabf7dd092b0687/manifests/gitkube-setup.yaml#L93 https://github.com/hasura/gitkube/blob/7d0e7f25b811d48089b78...