# Installing Rancher on Azure

**URL:** <https://forums.suse.com/t/installing-rancher-on-azure/3580>\
**Category:** Rancher 1.x\
**Created:** [July 29, 2016, 3:44pm UTC](https://forums.suse.com/t/installing-rancher-on-azure/3580 "2016-07-29T15:44:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![chent](https://avatars.discourse-cdn.com/v4/letter/c/e19adc/32.png) [@chent](https://forums.suse.com/u/chent)\
**Post date:** [July 29, 2016, 3:44pm UTC](https://forums.suse.com/t/installing-rancher-on-azure/3580/1 "2016-07-29T15:44:24Z")

</div>

Hi there,

I’m currently using docker cloud and thought I’d give rancher a shot.

I followed the single node setup guide but I can’t access the UI.

Here’s what I did:

1. Provision a VM - Ubuntu Xenial
2. Install docker - test containers work fine
3. Follow instructions “Installing Rancher Server (Single Node)” - my docker command is  
`sudo docker run -d -v /srv/rancher/data:/var/lib/mysql --restart=always -p 8080:8080 rancher/server:stable`
4. Open port 8080 for the Azure VM

It seems the container is stuck on a DB setup step, looking at the container logs I see the following last entry:  
`time="2016-07-29T15:25:15Z" level=info msg="Creating schema machine, roles [readonly]" id=1ds20`

Can anyone offer any advice as to why this might be happening?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [July 29, 2016, 4:10pm UTC](https://forums.suse.com/t/installing-rancher-on-azure/3580/2 "2016-07-29T16:10:31Z")

</div>

Can you share your full logs from the rancher/server container?

---

<div class="post-metadata">

**Author:** ![chent](https://avatars.discourse-cdn.com/v4/letter/c/e19adc/32.png) [@chent](https://forums.suse.com/u/chent)\
**Post date:** [July 29, 2016, 6:12pm UTC](https://forums.suse.com/t/installing-rancher-on-azure/3580/3 "2016-07-29T18:12:21Z")

</div>

Hi there,

I traced the issue to the network security group in Azure.

Everything is working great, just testing out some stacks now.

Thanks for getting back!