I have followed all the instructions listed on the Mikrotik container page. Every time I try to load a container I get an error.

I am using the command "/container/add remote-image=linuxserver/unifi-controller interface=veth1 root-dir=disk1/unifi" to load the container but I just get an error. (See attached Picture)

download/file.php?mode=view&id=63211

Any suggestions?

Thank you in advance.

What does the log specifically say?

The log says there's no version of the Unifi container that will load on that particular CPU.

From https://gist.github.com/jasco/2d39fdc80 ... 5d0e09c116:

"The instructions for setting up the Unifi Controller on ARM do not cover ARM64. The documentation states that ARM64 is not supported but hints it can be setup manually. The documentation also states that Java 8 is currently required."

So you might need to build the container yourself and transfer it over.

Generally before start deploying container check on Docker Hub (when Docker registry is used) if specific tag for container image supports your device CPU architecture which is ARM (32-bit) by looking at device product page, image should have builds for linux/arm/v6 or linux/arm/v7 architectures, in this case latest tag (latest tag is fetched if not specified for remote image) in unifi-controller tags have builds only for linux/amd64 (x86-64) and linux/arm64 (ARM64) and that is reason of this error, your device architecture is not supported for this image tag.

Some container images can have different tag for some architecture, like older version tag when latest build is made for arhitecture supported by your device, you can try to filter tags by arm or arm32 keywords to find it, example https://hub.docker.com/r/linuxserver/un ... name=arm32 and you can see there is arm32v7-7.3.83 latest tag with supported arch (there is also arm32v7-latest and arm32v7-mongoless tags but with wrong arch), if that older version suits you, you can try to add container with remote image .