Unifi controller on Mikrotik RB5009 7.9

RouterOS Beginner Basics
1

Hi !
I have issue with installing container to rb5009 with 7.9
Unifi controller on mikrotik were working perfectly before using this script :

/system/device-mode/update container=yes
/interface/veth/add name=veth1-unifi address=192.168.88.10/24 gateway=192.168.88.1
/interface/bridge/port add bridge=bridge interface=veth1-unifi
/container config set registry-url=https://registry-1.docker.io tmpdir=disk1
/container/config/set ram-high=600M
/container/mounts add dst=/config name=unifi-controller_config src=/disk1/containers/unifi-controller/config
/container add remote-image=jacobalberty/unifi:latest hostname=unifi interface=veth1-unifi logging=yes mounts=unifi-controller_config root-dir=disk1/containers/unifi-controller workdir=disk1/containers/unifi

After extracting procedure
extracting.png
It writes stoped
Even after I try to run it with:

/container start 0

it won’t start

Does anybody have any idea how to fix it ?

2

What does unifi controller have to do with a container issue??

3

That the code is running on routerOS 7.8 :slight_smile:

4

I don’t have any experience with Unifi … but I’ve read in another thread that Unifi controler is a pretty fat application which requires more than 1GB RAM to run. RB5009 has only got 1GB (and some of it is required to run ROS and do some firewalling/routing). So it might be that unifi controller is simply too fat to be run on RB5009 (and many other, most Mikrotiks come with 1GB of RAM or less).

5

That is what I think in new routerOS is memory handling more safe…

It is definitely true that all unifi consoles have at least 2Gb RAM.
But for example Banana Pi device with 1Gb ram can run unifi controller and managment of 35 devices wothout any issue.

And there is one more thing
The container was running on older routerOS.

6

I cannot see docker being that intensive… If I was docker conversant I could help as probably the error is there in your config.