kubernetes: Could not connect to rsync container. See build/README.md for setting up remote Docker engine.

I have symptoms that look like those being fixed by this: https://github.com/kubernetes/kubernetes/pull/34288 but I still get the error after cherry-picking that fix.

The last two commits in my tree are:

15b9583a713d4fd81aa446cceb224b94cfc62d3a (aka https://github.com/kubernetes/kubernetes/pull/34257)
a cherry pick of https://github.com/kubernetes/kubernetes/pull/34288

I have removed all containers and images from my system. I’m in a clean git tree.

I run make clean; make release and get the following out:

+++ [1006 20:34:06] Verifying Prerequisites....
+++ [1006 20:34:06] Building Docker image kube-build:build-be4685d15b-4-v1.6.3-9
+++ [1006 20:35:42] Creating data container kube-build-data-be4685d15b-4-v1.6.3-9                                                                                                                               +++ [1006 20:35:44] Syncing sources to container
!!! [1006 20:35:49] Could not connect to rsync container. See build/README.md for setting up remote Docker engine.
make: *** [Makefile:239: release] Error 1

When I try to investigate…

$ docker ps -a

CONTAINER ID        IMAGE                                    COMMAND                  CREATED              STATUS                      PORTS                       NAMES
43529d54bfce        kube-build:build-be4685d15b-4-v1.6.3-9   "/rsyncd.sh"             58 seconds ago       Up 57 seconds               127.0.0.1:32776->8730/tcp   kube-rsync-be4685d15b-4-v1.6.3-9
e18d40dbcba6        kube-build:build-be4685d15b-4-v1.6.3-9   "chown -R 1000.1000 /"   About a minute ago   Exited (0) 58 seconds ago                               kube-build-data-be4685d15b-4-v1.6.3-9

$ docker logs 435
2016/10/06 20:35:45 [1] rsyncd version 3.1.1 starting, listening on port 8730

I’m happy to try anything for the sake of troubleshooting/debugging. Thanks.

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 15 (13 by maintainers)

Commits related to this issue

Merge pull request #34351 from jbeda/verify-rsync Automatic merge from submit-queue Check for rsync and give friendlier message Fixes #34300. Not sure if #34309 is the same issue. Hopefully it ... — committed to kubernetes/kubernetes by deleted user 8 years ago

Most upvoted comments

I also encounter this issue and it’s because docker for mac reverses 64G disk size for all images and containers. And mine is already using 60G so rsync container cannot get started. Run this command to free up space. “docker system prune -a --volumes”

levimm on Aug 10, 2019

@colemickens I encounter the same problems as you said above on release-1.5 branch, but I have installed the rsync, how to fix it? or something else I missed?

root@heatonli-test1:/home/zhangjian/src/k8s.io/kubernetes#docker ps -a
CONTAINER ID        IMAGE                                    COMMAND                  CREATED             STATUS                    PORTS                       NAMES
ef046989690c        kube-build:build-da00aed54b-4-v1.7.4-0   "/rsyncd.sh"             15 hours ago        Up 15 hours               127.0.0.1:32771->8730/tcp   kube-rsync-da00aed54b-4-v1.7.4-0
d950352b60ee        kube-build:build-da00aed54b-4-v1.7.4-0   "chown -R 0.0 /go/src"   15 hours ago        Exited (0) 15 hours ago                               kube-build-data-da00aed54b-4-v1.7.4-0

root@heatonli-test1:/home/zhangjian/src/k8s.io/kubernetes#which rsync
/usr/bin/rsync
root@heatonli-test1:/home/zhangjian/src/k8s.io/kubernetes# go version
go version go1.7.4 linux/amd64

jianzhangbjz on Jan 12, 2017