Running rancher/server (or any container) on RancherOS on GCE needs MTU configured to 1460 #8910
Comments
|
Same here… |
GatoSnake
changed the title
|
Now I installed rancher in CoreOS stable provided by GCE and rancher works nice, I can access to UI via browser with the public IP. I think that the problem is RancherOS with GCE. |
|
What's the problem? you can't access to the WEB UI? or RancherOS doesn't start up at all? if so, what kind of instance you launching? It doesn't seem to work on f1-micro, fyi
Klud
…On May 29, 2017, 22:06 -0400, Cristhian Won ***@***.***>, wrote:
Now I installed rancher in CoreOS stable provided by GCE and rancher works nice, I can access to UI via browser with the public IP.
I think that the problem is RancherOS with GCE.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Hi @klud1 ,
The specifications of the instance is: |
|
that's weird, though perhaps you didn't open the http ports, apply the firewall rules
…On May 29, 2017, 22:15 -0400, Cristhian Won ***@***.***>, wrote:
Hi @klud1 ,
1. I can't access to the WEB UI with the public IP of the instance. RancherOS start fine.
The specifications of the instance is:
n1-standard-1 (1 vCPU, 3,75 GB memory)
Intel Sandy Bridge
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I have opened the http ports, specially the 8080. I use same firewall rules for CoreOS and it works.
The problem just happened using rancher with RancherOS in GCE :/ |
|
Your're right. Altough i faced a similar problem yesterday, i was giving a try to GCE to host some personal projects and stuff, thing is i was trying to serve some services behind nginx, the containers were running, i was able to reach nginx on the VM's public ip but i couldn't reach the vhosts, not even with curl, i finally gave up. :( But in your case, you're just using the public ip, so it shouldn't be a problem, that's pretty weird actually. |
|
Well, thanks you @klud1 .. for this moment I will use CoreOS, works nice with rancher. |
|
De nada, perro! I'll give a try to your use-case (when i get some free time) and see if i can get it working, i'm using RancherOS on premises atm, i'm launching a couple of instances these days and then give you some feedback in case i succeed (^_^) |
|
@klud1 excelente compa! ... thanks for all 😄 |
aemneina
added
area/server
kind/question
|
Sorry for the delay, been a bit busy, i'm trying this now...and you're right, can't reach the UI on GCE even though firewall rules are ok. |
|
Can you please try the following so we can get this fixed.
|
|
Alright, that did the trick! tysm, @superseb |
superseb
changed the title
superseb
added
area/documentation
kind/task
|
This should be fixed via rancher/os#2027 |
Rancher versions:
rancher/server: 1.6.0 (latest)
rancher/agent: N/A
Infrastructure Stack versions:
healthcheck: N/A
ipsec: N/A
network-services: N/A
scheduler: N/A
kubernetes (if applicable): N/A
Docker version: (
docker version,docker infopreferred)Operating system and kernel: (
cat /etc/os-release,uname -rpreferred)Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
GCE (Google Cloud Engine)
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node rancher
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
N/A
Steps to Reproduce:
Create a new instance using the new disk with RancheOS installed.
Install Rancher server latest version with the next command:
sudo docker run -d --restart=unless-stopped -p 8080:8080 --name rancher-server rancher/serverResults:
Access from browser to http://x.x.x.x:8080/ and stuck in "Loading ..." UI with the page in white.
But ..
if I access to the machine via Tunnel SSH and I access to the url http://localhost:8080/, I can access to the rancher server UI and it works fine.
Logs
The text was updated successfully, but these errors were encountered: