google cloud shell support
matti opened this issue · 7 comments
matti commented
script fails on google cloud shell machine:
./dind-cluster-v1.12.sh up
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
* Making sure DIND image is up to date
v1.12: Pulling from mirantis/kubeadm-dind-cluster
Digest: sha256:8c3685e45747d09a336a8844d65d7e93d38d036b284b427d0a2a6596808cee88
Status: Image is up to date for mirantis/kubeadm-dind-cluster:v1.12
* Starting DIND container: kube-master
* Running kubeadm: init --config /etc/kubeadm.conf --ignore-preflight-errors=all
Initializing machine ID from random generator.
A dependency job for docker.service failed. See 'journalctl -xe' for details.
docker failed to start. Diagnostics below:
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled)
Active: inactive (dead) since Tue 2018-12-04 21:45:36 UTC; 4ms ago
Docs: https://docs.docker.com
Process: 67 ExecStart=/usr/local/bin/rundocker (code=killed, signal=TERM)
Main PID: 67 (code=killed, signal=TERM)
Tasks: 1
Memory: 400.0K
CPU: 4ms
CGroup: /kubepods/besteffort/podc726c0d8ff3eb6f4e5c967a0662793d1/7e14fa281d83676dd6862c90d09b176e2c49df8bf30cd67885829826185d3632/docker/348778ef2398c87fa6b318d77a12c4e4c4c93ff54e2172766c6423f4eeb71de0/system.slice/docker.service
Dec 04 21:45:36 kube-master systemd[1]: Starting Docker Application Container Engine...
Dec 04 21:45:36 kube-master systemd[1]: Dependency failed for Docker Application Container Engine.
Dec 04 21:45:36 kube-master systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'.
Dec 04 21:45:36 kube-master systemd[1]: Stopped Docker Application Container Engine.
*** kubeadm failed
alexmt commented
I've got the same error with while trying to run it inside kubernetes pod. Docker daemon runs as a sidecar:
dind-cluster-v1.13.sh up logs
./dind-cluster-v1.13.sh up
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
* Making sure DIND image is up to date
sha256:0fcb655948a1fa20f5a2100983755edc8f0d763248bda217b3454d82d5cd3be4: Pulling from mirantis/kubeadm-dind-cluster
d2519f41f710: Pull complete
62bc77b5a5bc: Pull complete
89361b6165e2: Pull complete
63fac53415a9: Pull complete
930aa6818f06: Pull complete
bd4bee337c9c: Pull complete
5c49605ff573: Pull complete
0e26591e6f37: Pull complete
cd34b4ad9820: Pull complete
713c4fd4a18c: Pull complete
ecf1b01d2e76: Pull complete
9f01d4f32321: Pull complete
d766b8e7abcf: Pull complete
666d57260e9c: Pull complete
ad4ef8b461d7: Pull complete
7edb5a935ce0: Pull complete
919e68ed781c: Pull complete
83c7a2d995dc: Pull complete
44506f621f1a: Pull complete
fb1598ae72e5: Pull complete
a096241fe1bf: Pull complete
21a3b05a94d6: Pull complete
ccef30e9fc36: Pull complete
3cdb2a50b191: Pull complete
3a9ba5b20a8a: Pull complete
0ccf60639047: Pull complete
Digest: sha256:0fcb655948a1fa20f5a2100983755edc8f0d763248bda217b3454d82d5cd3be4
Status: Downloaded newer image for mirantis/kubeadm-dind-cluster@sha256:0fcb655948a1fa20f5a2100983755edc8f0d763248bda217b3454d82d5cd3be4
/root/.kubeadm-dind-cluster/kubectl-v1.13.0: OK
* Starting DIND container: kube-master
* Running kubeadm: init --config /etc/kubeadm.conf --ignore-preflight-errors=all
Initializing machine ID from random generator.
A dependency job for docker.service failed. See 'journalctl -xe' for details.
docker failed to start. Diagnostics below:
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled)
Active: inactive (dead) since Wed 2019-01-09 17:53:55 UTC; 10ms ago
Docs: https://docs.docker.com
Process: 78 ExecStart=/usr/local/bin/rundocker (code=killed, signal=TERM)
Main PID: 78 (code=killed, signal=TERM)
Tasks: 1
Memory: 196.0K
CPU: 6ms
CGroup: /kubepods/burstable/pod5e360f58-1437-11e9-b4ce-42010a8001e6/e52fbe607d0937662087dc504408090556494d193bd0a937b490049f219dc552/docker/e0c69d628ae4de306325360d0aeb7c5781d95ec707c8ab85f0ca0794aa4b06c9/system.slice/docker.service
Jan 09 17:53:54 kube-master systemd[1]: Starting Docker Application Container Engine...
Jan 09 17:53:55 kube-master systemd[1]: Dependency failed for Docker Application Container Engine.
Jan 09 17:53:55 kube-master systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'.
Jan 09 17:53:55 kube-master systemd[1]: Stopped Docker Application Container Engine.
*** kubeadm failed
journalctl logs
root@kube-master:/# journalctl -xe
WARNING: terminal is not fully functional
Jan 09 17:53:55 kube-master dindnet[77]: "isDefaultGateway": true,
Jan 09 17:53:55 kube-master dindnet[77]: "hairpinMode": false,
Jan 09 17:53:55 kube-master dindnet[77]: "ipMasq": true,
Jan 09 17:53:55 kube-master dindnet[77]: "ipam": {
Jan 09 17:53:55 kube-master dindnet[77]: "type": "host-local",
Jan 09 17:53:55 kube-master dindnet[77]: "ranges": [
Jan 09 17:53:55 kube-master dindnet[77]: [
Jan 09 17:53:55 kube-master dindnet[77]: {
Jan 09 17:53:55 kube-master dindnet[77]: "subnet": "10.244.1.0/24",
Jan 09 17:53:55 kube-master dindnet[77]: "gateway": "10.244.1.1"
Jan 09 17:53:55 kube-master dindnet[77]: }
Jan 09 17:53:55 kube-master dindnet[77]: ]
Jan 09 17:53:55 kube-master dindnet[77]: ],
Jan 09 17:53:55 kube-master dindnet[77]: "routes": [
Jan 09 17:53:55 kube-master dindnet[77]: {
Jan 09 17:53:55 kube-master dindnet[77]: "dst": "0.0.0.0/0"
Jan 09 17:53:55 kube-master dindnet[77]: }
Jan 09 17:53:55 kube-master dindnet[77]: ]
Jan 09 17:53:55 kube-master dindnet[77]: }
Jan 09 17:53:55 kube-master dindnet[77]: }'
Jan 09 17:53:55 kube-master dindnet[77]: + echo 'Config file created: /etc/cni/net.d/cni.conf'
Jan 09 17:53:55 kube-master dindnet[77]: Config file created: /etc/cni/net.d/cni.conf
Jan 09 17:53:55 kube-master dindnet[77]: + dind::make-kubelet-extra-dns-args
Jan 09 17:53:55 kube-master dindnet[77]: + [[ ipv4 = \i\p\v\6 ]]
Jan 09 17:53:55 kube-master dindnet[77]: + grep -q '#fixed#' /etc/resolv.conf
Jan 09 17:53:55 kube-master dindnet[77]: ++ awk '/^nameserver/ {print $2; exit}' /etc/resolv.conf
Jan 09 17:53:55 kube-master dindnet[77]: + old_ns=127.0.0.11
Jan 09 17:53:55 kube-master dindnet[77]: + [[ -z 127.0.0.11 ]]
Jan 09 17:53:55 kube-master dindnet[77]: + sed 's/^nameserver.*/nameserver 10.192.0.2/' /etc/resolv.conf
Jan 09 17:53:55 kube-master dindnet[77]: + cp /etc/resolv.conf /etc/resolv.conf.orig
Jan 09 17:53:55 kube-master dindnet[77]: + cat /etc/resolv.conf.updated
Jan 09 17:53:55 kube-master dindnet[77]: + echo
Jan 09 17:53:55 kube-master dindnet[77]: + echo '#fixed#'
Jan 09 17:53:55 kube-master dindnet[77]: + echo 'Setup completed for ipv4 mode'
Jan 09 17:53:55 kube-master dindnet[77]: Setup completed for ipv4 mode
Jan 09 17:53:55 kube-master dindnet[77]: + true
Jan 09 17:53:55 kube-master dindnet[77]: + socat udp4-recvfrom:53,reuseaddr,fork,bind=10.192.0.2 UDP:127.0.0.11:53
Jan 09 17:55:24 kube-master systemd[1]: dev-sda1.device: Job dev-sda1.device/start timed out.
Jan 09 17:55:24 kube-master systemd[1]: Timed out waiting for device /dev/sda1.
-- Subject: Unit dev-sda1.device has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit dev-sda1.device has failed.
--
-- The result is timeout.
Jan 09 17:55:24 kube-master systemd[1]: dev-sda1.device: Job dev-sda1.device/start failed with result 'timeout'.
Jan 09 17:55:24 kube-master systemd[1]: Startup finished in 1min 30.209s.
Is it #255 or remote docker daemon is not supported as mentioned in #235 ?
ivan4th commented
Could you also paste the result of
journalctl -xe -n all -u docker.service
from the kube-master node?
Also I'd say this looks suspicious:
Jan 09 17:55:24 kube-master systemd[1]: dev-sda1.device: Job dev-sda1.device/start timed out.
Jan 09 17:55:24 kube-master systemd[1]: Timed out waiting for device /dev/sda1.
@bobhenkel just verified on my mac and kdc works just fine there. I have High Sierra though.
Does inner dockerd fail in your case too? In this case, the output of
docker exec kube-master journalctl -xe -n all -u docker.service
would be nice, too.
I also use remote docker all the time (tried against remote bare metal machines, GCE instances, CircleCI remote docker etc.) and it works for me just fine.
fejta-bot commented
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot commented
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
fejta-bot commented
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
k8s-ci-robot commented
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.