@nzben QNAP TS-431 - it is supported in the product notes, but at a certain point has been disabled

"....However, I was a bit disappointed to learn that QNAP has decided not to support Container Station, among others [1], in the 4.3.3 release of QTS for the TS-431.

From what I understand, and please correct me if I am wrong, there seem to be 2 issues preventing support.

1) The fairly old version version of the Linux kernel[2] that ships with QTS
2) The unpleasantness of building and linking Docker within the QTS environment...."

  @d0ugmac1 have managed to get Docker Desktop on the mac mini - ver 4.15.0 (93002) as the latest version doesnt support my mini's OS version

  @d0ugmac1 

Hi thanks for this. I have had a try at setting this up but seems unsuccessful in that I cant open the Omada Controller at the end - I get the message in my browser:

"Cant Connect to server "https://localhost:8043" because Safari cant connect to server "localhost".

I have tried the various itterations of the address with the same result.

A few things;

The host computer is a 2012 Mac Mini Server wtih a 2.3 GHz Quad-Core Intel Core i7 and 8GB RAM. Its stuck on Catalina OS X 10, which means the Docker Desktop I can get running is ver 4.15.0 (93002), so looks a little different to your screengrabs, but seems to work.

On the Container Image download the highest version I can get is 5.9 Chromium  - beta isnt listed.

Once again, everything works but looks a little different.

One the first step where I name the container, and the port information is there, those boxes are all blank. Should I be entering numbers here and if so what? I left them blank as I was unsure, and eveything seems to work. It went through many lines in the LOG but I did manage to find the equivalnet lines that you highlighted.

Im the summary page, I can see CPU and RAM is being used and the container is running, however under Ports it is blank - does this mean the ports havnt been asigned correctly?

BR

As above, in the final step I cant connect via the browser.

  @d0ugmac1 after a few more attempts and entering the port numbers manually Ive managed to get up and running, now to try and get the network configured, so far Im having a few issues with the EAPs but seem to recall seeing that they need to be hardware reset before setting up.

  @d0ugmac1 Hi.

Ive sucessfully managed to get my 225 Outdoor V1 connected to the omada controller, but the 225 indoor V2 comes up as "this device is not compatible with the current controller"

Controller version is 5.9.31

EAP 225 Indor V2 is running 1.4.0 Build 180323

Is it possible that this hardware is just too old and wont work?

  @d0ugmac1 ive done a bit more digging and it appears that they came up with a V3, at whcih point the V2 stopped getting any updates hence the 2018 and is not supported by the controller software.

Ironically the 225outdoor I have is a v1, and it was released around the same time but is still getting updates and is supported.... Go figure, perhaps I need to find myself a newer indoor unit