Hi @BarryV2021 That environment appears to be your local environment as it's uding the Docker socket. I am assuming that you only have one instance of Portainer running without any other hosts attached via agents. So seeing the single primary makes sense.

It should be called local, but I know some NAS providers tweak the deployments and don't use the offical images and use their own.

It seems like that Portainer package installed another version of docker, not connected to Container station, Portainer needs to be deployed with the appropriate socket so Portainer can read the correct docker environment. It seems like ways of deploying Portainer on QNAP NAS's has been discussed here. - https://www.reddit.com/r/qnap/comments/11avf03/qnap_portainer_setup_for_a_noob/

If this doesn't sound right, please break down your expectation and how it was previsoluy before you redeployed Portainer.

Hi @Nick-Portainer: I installed Portainer from the MyQNAP repository and then I don't see the local environment. Previously when I install the portainer from the MyQNAP repository it was created and I saw the two environments local and primary (seee attachments). When I follow the guide mentioned in your reply it only creates the local environment.

See here the pictures of the original install from MyQNAP repository the first time:

You would only want the one local environment right? I can see the local is also reporting all the containers you have running as well. So looks good