unifi docker will not run

Follow

Gil

• November 13, 2021 02:44
• Edited

I am following the instructions for the unifi docker install and after creating the docker-compose.yaml file, when I run the "sudo systemctl start docker-compose@unifi" command to start the unifi docker, it doesn't do anything. So I ran the "sudo docker-compose up -d" command and when I do that, I get the following error:

ERROR: stat /var/lib/docker/overlay2/ae5c789212afc89ad9d4eb7e7abcf145f3bd6c7822df7dfad4241809c9b93a0d: no such file or directory

When I run the "sudo docker ps" command, no dockers are running. I checked the docker image library and it looks like it got the unifi docker image. I am creating a new subnet for the docker subnet as stated in the documentation, and I am using the example subnet of 172.16.1.0/24

0

• 

  Michael Bierman

  • January 08, 2022 04:25

  Were you able to get this resolved? 

  0

  Comment actions Permalink
• 

  Gil

  • January 08, 2022 17:16

  Nope. Support won't help me either.

  0

  Comment actions Permalink
• 

  privero231

  • October 09, 2022 22:09

  Does anyone know the terminal command in Firewalla Gold for showing the docker containers?

  0

  Comment actions Permalink
• 

  Michael Bierman

  • October 09, 2022 23:00
  • Edited

  @Privero231

  sudo docker container ls 

  will show the current containers and how long they have been up. 

   

  https://www.designcise.com/web/tutorial/is-there-any-difference-between-docker-ps-and-docker-container-ls-commands#:~:text=There%20is%20no%20difference%20between,more%20verbose%20than%20the%20former.

  0

  Comment actions Permalink
• 

  privero231

  • October 09, 2022 23:10

  I ran the command you suggested and it shows that I don't have any docker containers

  0

  Comment actions Permalink
• 

  privero231

  • October 10, 2022 01:41

  Okay I installed it but when I log on and check my devices it says my Access Point is offline

  0

  Comment actions Permalink
• 

  privero231

  • October 10, 2022 18:32

  When I log in ssh it says IP address for docker0 is 172.17.0.1

  0

  Comment actions Permalink
• 

  Michael Bierman

  • October 10, 2022 21:39

  You are running the unifi docker container? What is in your YAML file? Did you use the one provided by Firewalla?

  0

  Comment actions Permalink
• 

  privero231

  • October 12, 2022 14:05

  yes and I deleted the file  /home/pi/.firewalla/run/docker/docker-container.yaml.

  Still when I run sudo docker container ls it gives me an output that it is running and healthy. image: jacobalberty/unifi:latest

  Also I was messing around and changed the subnet of the network where my unifi access was from 192.168.1.0/24 to 172.16.1.0/24

  Now there is an entry for  IP address for br-c39bf2638d6e: 172.16.1.1

  And also there is IP address for br1:             172.16.1.1

   

  0

  Comment actions Permalink
• 

  privero231

  • October 12, 2022 21:41

  Ok I was able to remove the mess I made. Thanks. One more question, does the docker container have to be the same local network where I have my Unifi Access Point installed?

  0

  Comment actions Permalink
• 

  Michael Bierman

  • October 13, 2022 01:33

  Best to either follow the firewalla tutorial or use this script which does that for you. github.com/mbierman/unifi-installer-for-Firewalla

  0

  Comment actions Permalink
• 

  privero231

  • October 13, 2022 02:17

  The script on GitHub.com installs unifi in network 172.16.1.0/24. Does that mean that I have to use that IP address for my unifi access points or is it routable through the Firewalla Gold? For example: I have my Unifi access point in network 192.168.1.0/24. Will I be able to adopt the access point if I ssh into the access point and set the inform url to point to https://172.16.1.2:8443.

  Thank you in advance.

  0

  Comment actions Permalink
• 

  David Rothenberger

  • October 13, 2022 03:12

  For example: I have my Unifi access point in network 192.168.1.0/24. Will I be able to adopt the access point if I ssh into the access point and set the inform url to point to https://172.16.1.2:8443.

  I believe that's the right approach. Leave your APs in their current network and use L3 adoption to your controller at 172.16.1.2.

  I suggest adding a DNS entry for "unifi" (no domain), since the APs will automatically do an L3 adoption to that server if it resolves. See https://help.firewalla.com/hc/en-us/articles/360056024294-Guide-How-to-customize-Firewalla-DNS-service for how to add the DNS entry.

  0

  Comment actions Permalink
• 

  privero231

  • October 13, 2022 05:01

  I want to thank you very much for all your help. I finally got it working perfectly and I can access it right from my mobile phone through the internet and I have not forwarded any ports. I am going to setup OpenVPN for my laptop so that I can remote in and login to the Unifi network application.
  Again, a million thanks 👍👍👍

  0

  Comment actions Permalink

Please sign in to leave a comment.