Closed PerlStalker closed 5 years ago
Can the rke
user on the Ubuntu machine use Docker? What happens if you run sudo -u rke docker version
there?
Also (and unrelated), maybe it is better to use the overlay2 driver instead of aufs?
That was the first thing I checked. It works just fine.
$ ssh rke@kube01 docker version
Client:
Version: 17.03.2-ce
API version: 1.27
Go version: go1.7.5
Git commit: f5ec1e2
Built: Tue Jun 27 03:35:14 2017
OS/Arch: linux/amd64
Server:
Version: 17.03.2-ce
API version: 1.27 (minimum version 1.12)
Go version: go1.7.5
Git commit: f5ec1e2
Built: Tue Jun 27 03:35:14 2017
OS/Arch: linux/amd64
Experimental: false
I doubt the storage driver has anything to do with my current problem but I'll keep it mind.
I'm pretty sure I'm seeing this as well.
$ docker version
Client:
Version: 17.03.2-ce
API version: 1.27
Go version: go1.7.5
Git commit: f5ec1e2
Built: Tue Jun 27 03:35:14 2017
OS/Arch: linux/amd64
Server:
Version: 17.03.2-ce
API version: 1.27 (minimum version 1.12)
Go version: go1.7.5
Git commit: f5ec1e2
Built: Tue Jun 27 03:35:14 2017
OS/Arch: linux/amd64
Experimental: false
on this initial error:
INFO[0000] [dialer] Setup tunnel for host [10.12.194.32]
WARN[0075] Failed to set up SSH tunneling for host [10.12.194.32]: Can't retrieve Docker Info: error during connect: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.24/info: Unable to access node with address [10.12.194.32:22] using SSH. Please check if the node is up and is accepting SSH connections or check network policies and firewall rules. Error: dial tcp 10.12.194.32:22: getsockopt: operation timed out
this attempt was made with rke_darwin-amd64-v0.1.11
Please share OS information used as well.
@PerlStalker Can you also try using an IP address to rule out certain things. Also if you can post the contents of /etc/hosts
, ip a s
and ip route
, there might be something there.
@superseb os info:
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial
@PerlStalker I like the socat verification you were doing. I attempted it myself to see if I'm seeing the exact same thing. Alas, I'm not. Though the rke response is the same, I'm not seeing anything on /var/run/docker.sock while rke is running. I do see info on /var/run/docker.sock if I'm on the remote machine and just run docker ps
.
Other troubleshooting: started up a vagrant guest locally and tried with rke_linux-amd64-v0.1.11; same error.
So... solved my issue. Was moving too fast and just changed 'hostname_override' when updating cluster config, ignoring 'address'. Primarily, this is user error.
That said, I'm now curious why address must be specified as ip. But so as to not derail the thread, I'll open a separate issue. follow-up: it doesn't. 'address' can be a hostname.
Unfortunately, I've torn down that environment so I can no longer test. I guess you can close this.
On Tue, Oct 30, 2018 at 10:47 AM Hefeweizen notifications@github.com wrote:
@superseb https://github.com/superseb os info:
lsb_release -a
No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial
@PerlStalker https://github.com/PerlStalker I like the socat verification you were doing. I attempted it myself to see if I'm seeing the exact same thing. Alas, I'm not. Though the rke response is the same, I'm not seeing anything on /var/run/docker.sock while rke is running. I do see info on /var/run/docker.sock if I'm on the remote machine and just run docker ps.
Other troubleshooting: started up a vagrant guest locally and tried with rke_linux-amd64-v0.1.11; same error.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rancher/rke/issues/872#issuecomment-434378353, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLKrA5XhRJapumIo2g0e3Xk8PoTSEUHks5uqIKogaJpZM4WExC1 .
-- Randall Smith http://www.musicfreestatic.com/ KE0NDF
same problem here! In my case, this daemon didn't run: "ssh_agent_auth: false"
RKE version:
rke version v0.1.9
Docker version: (
docker version
,docker info
preferred)Operating system and kernel: (
cat /etc/os-release
,uname -r
preferred)Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Linux KVM
cluster.yml file:
Steps to Reproduce:
rke -d up --config cluster-test.yml
Results:
Attempting to bring up a new cluster fails. The warning claims that it failed to setup ssh tunneling and that it can't connect to the Docker socket. The message is below.
The troubleshooting guide suggests that it's a problem with the address or port. However, I have verified that rke is successfully logging in with ssh and connecting to the docker using
socat
to sniff the API socket.The output is below.
As you can see, rke is connecting to Docker and running
docker info
. The response is being sent back but rke isn't seeing it. The result is that rke is unable to successfully start a new cluster.