Closed googleg closed 1 year ago
Thanks for the information!
So, you don't recommend rebuilding & republishing the image if I'm right, because the version in the image seems to work?
The image uses https://dl.google.com/linux/direct/chrome-remote-desktop_current_amd64.deb link to download the package during build process. Maybe you are aware of a link that can be used to pin the exact version?
You are 100% correct the image uses a link to the latest version, so at build time the latest available version is pulled and embedded.
Unfortunately Google does not publish direct links to older versions. I hoped that I could substitute the release number of an older version in the direct link to the current version, but it does not work. The direct link to the current release is https://dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/chrome-remote-desktop_116.0.5845.9_amd64.deb
Luckily I've found a mirror that keeps history of old versions: https://deb.rug.nl/ppa/mirror/dl.google.com/linux/chrome-remote-desktop/deb/pool/main/c/chrome-remote-desktop/
So for now to avoid problems do not rebuild the image nor update the package chrome-remote-desktop from within a running container.
ok, let's keep it as it is since an image on Docker Hub seem to work. The only downside is if you try to build an image from Dockerfile it will not work. If you track the progress of this issue, please let me know here when it gets fixed. If they don't fix it in some month, I will replace the link to point to the mirror you suggested.
Thanks!
Sure, I'll keep you posted. I have raised the issue to Google, not that I am expecting an answer but hopefully this will help them realize they made a snafu.
Quick update: Google has published a new version of the package, 116.0.5845.10, which fixes one problem in the code but there is another bug in the code that still prevents the service to start properly.
I have reported it once again, let's see if they can finally fix it.
I have the impression they are not testing before releasing, quite scary.
Ok folks, good news, the problem seems to have been fixed in the latest update of the package released on 29th September:
chrome-remote-desktop_118.0.5993.9_amd64.deb
I am closing the issue.
Thanks for the update
Just a quick note to mention that the latest upgrade of the chrome-remote-desktop linux package has a bug that prevents the remote desktop server from starting.
There is a problem with the file /opt/google/chrome-remote-desktop/chrome-remote-desktop. This is a Python script that cannot be executed:
I am happy to confirm that there is a work-around which is overwriting the faulty script /opt/google/chrome-remote-desktop/chrome-remote-desktop with an earlier version.
I did not notice any obvious side effect of using an older script, for now.
I do not think I can add the working version of the file here as it is licensed by Google. We'll have to wait for them to fix the problem I guess.