Closed Dmitry1987 closed 4 years ago
lol sorry I just can't hold it 🤣 ... I'm back after my failed Rancher POC in 2016-2017 where we all had a ton of issues (we - are the K8s slack channel community who all tried Rancher/Kops/DCOS/Swarm/Nomad at the time, trying to pick a vendor for our company prod environments), to give it another chance, just to get it fail to load during "Quick start" official documentation steps? 🤣 It gives a real "Great success!" impression (c) Borat.
It worked for me, what's your problem? Currently, you are using Rancher2 not Rancher1.
@niusmallnan was this product built to work for you, or others as well? :)
The problem was:
You can think of it as a bug report. You were unable to reproduce, I understand, but it doesn't mean it didn't happen :)
@Dmitry1987 I run RancherOS v1.5.4 on Azure, and run Rancher2 on the RancherOS instance. I can access the UI via 80 and 443 port.
Apart from these error logs, can you show the specific phenomenon??
@niusmallnan you mean this one?
The thing just didn't run, what can I do... but nevermind, I already am trying it on ubuntu, it just didn't run on the RancherOS for some reason. I'm closing the issue.
RancherOS Version: (ros os version) Linux rancher-master 4.14.138-rancher #1 SMP Sat Aug 10 11:25:46 UTC 2019 x86_64 GNU/Linux
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.) Azure cloud.
**What's the problem*** I created the Rancher OS VM (2 cpu 7 ram) version 1.5.4 latest from Azure marketplace.
The following steps from the docs just don't work: https://rancher.com/docs/rancher/v2.x/en/quick-start-guide/deployment/quickstart-manual-setup/
Container logs are: