Again, it will be likely to complain about dependencies not present, so you probably have to run again: sudo apt-get -f install and then install CRD one more time like you just did above. deb where is the name of the deb file you just downloaded. Install it from command line: sudo dpkg -i. Then, as soon as that is set and done, search for the Linux Debian package of Chrome Remote Desktop and download it. (If you do not have a Google account, now is a good time to create one). You should find it from your "start" button in Ubuntu, but if it's not there, you'll find it under: /usr/share/applications/sktop It is important that you log in to Google using your Google account. Now that you have chrome installed, it is a good time to launch and test it. Then it is time to install Chrome Remote Desktop server (CRD). You solve this by typing: sudo apt-get -f install followed by another re-install of the chrome package again (just as you did above). During installation, it will most likely throw a lot of missing dependencies at you. deb Where is the name of the file you just downloaded from Google. Once downloaded, install it from command line using: sudo dpkg -i. Then launch Firefox from Ubuntu and goto where you search for Chrome download.
If everything is ok then the first thing to do is to update and upgrade sudo apt-get update sudo apt-get upgrade This takes time - be patient. So it is important to test this as soon as the container is up and running the first time. You will have to delete the whole container and start all over again. If your forget it now, or do it wrong, then I know of no way to change this later.
If you only need to have an easy transport of data in/out of the contianer, then a path to your Public folder is enough, but if you want to have full root folder access, then now is the time to set it up. This also must be done in the Advanced Setting -> Shared Folder during first time set up. Also, it is important to map a path to your QTS so that Ubuntu can easily stretch an arm and a leg out of the container and reach your QTS folder structure. You do this under Advanced Setting -> Network during first time setup. If you choose NAT, the container gets a new port each time you boot, and it becomes difficult to connect. During installation, it is important to choose host networking instead of NAT in order to let the container have access to your LAN subnet directly. I chose the docker-ubuntu-vnc-desktop image named "Ubuntu desktop with noVNC" in the CS repository. (If you have any idea, let the community know) However, my next idea was to install Ubuntu in Container station and then attempt to make CRD run from there. on-failure I talked to a couple of the chromium developers, but they could not help me. Eventually, I traced the problem down to PAM Authentication failure, see this link. I tried for some time to install and run CRD under Linux Station, but it failed persistantly when I tried to connect from a remote client with an "Invalid Key" error. As far as I know, there is no way to install and run CRD in QTS either as a QPKG or from Entware as OPKG.
Perhaps the easies way is to configure a Windows PC on the same LAN and use it as a front end, but that in turn requires yet another computer to run 24/7 probably also with UPS to be on the safe side. In theory, it should be easy to set up and configure, but in practice it can be quite challenging. If you want full access to your NAS without the need to open any ports in your WAN router, while still maintaining encryption and security, Chrome Remote Desktop is a wonderful tool. It requires no firewall opening or port forward, and can easily be secured using private or public sertifactes (SSL) However, the cloudlink service only gets you into QTS without any SSH or FTP or much of anything, and is not offered with a 24/7 guarantee. Access NAS using Chrome Remote Desktop (CRD) An easy (and secure) way to remotely access a QNAP NAS is to use MyQNAPCloud Cloudlink service.