Recently, I've experienced an error with running a Linux VM on Google Cloud Console. For some reason, noVNC will report that it can't connect to the server almost immediately.
This issue has only occurred recently, and I've simply been using the same line of code to run it, and it worked fine, until now.
My code in question is:
docker run -p 6080:80 -e RESOLUTION=1280x720 dorowu/ubuntu-desktop-lxde-vnc
Any ideas? I'm not very sure what I'm doing wrong.
Edit: I tested the code on a different device, it worked. Tested it on the other one, it did not. I'm now confused and don't know what to do.
Related
I'm getting this error whenever I try to run my project (with docker-compose) and cannot find any solution. I'm really hoping I've just been doing something dumb, so here goes...
I created a simple ASP.NET Core Web App (to test this out as I was having a problem on my "real" project.)
.Net Core 3.1
Visual Studio 16.11.3
Docker Desktop ver 4.0.1 (Docker Engine: 20.10.8)
Scenarios below were tried on both WSL2 and Hyper-V.
Docker itself is running fine, I can use containers no problem.
When I create the project with Docker support, I can run it fine (it creates the container, I can debug, etc)
If I add a docker-compose setup, however, I get the following error popup when I try run my project (from VS)
The only thing I can see in the output window (debug) is this:
The program '' has exited with code -1 (0xffffffff).
To be clear, the build was successful, the container is running in docker, etc.
After much effort, I found a way to get more information by running the following in the VS Command window:
DebugAdapterHost.Logging /On /OutputWindow
I now can see some more detail (in Output - Debug Adapter Host Log) but don't know how to solve it.
The most relevant message (afaik) is
1> ERROR: Debug adapter error output: /bin/sh: 1: /remote_debugger/vsdbg: not found
but here is the full output:
So I'm pretty stumped. I've uninstalled and reinstalled docker countless times, tried every imaginable setting, ensured everything is running with admin privileges, and so on.
In case it helps, here is my debug output from the same run (note how it says vsdbg is found)
Does anybody know what else I can try, or how to get more insight into this?
I´m facing the Problem that I can´t pull some Docker images and docker login also works just sometimes.
This occurs only under Windows 10 Pro. I also tested it under Linux and it worked with default configuration.
I´ve already searched for the solution here, but my network connection isn´t the problem, since Linux works on the same network and I also don´t use any Proxy Server which I have to configure.
I´m trying to execute docker pull postgres. The output is:
Error response from daemon: Get https://registry-1.docker.io/v2/library/postgres/manifests/latest: Get https://auth.docker.io/token?account=unkownuser&scope=repository%3Alibrary%2Fpostgres%3Apull&service=registry.docker.io: unexpected EOF
Other images fail also with the same error and sometimes even the docker login fails with the unexpected EOF error.
Everything worked fine since the last update.
I´ve already downgraded my version, but it didn´t help. I also tried to switch from windows to linux containers, no effect.
Does anybody else have this problem or did I do something wrong?
Do you use a FritzBox?
If yes try the following it helped me:
Log into your FritzBox
In the bottom left Corner is a Button called Content (I assume its called that. I got the German version which says "Inhalt")
Click "FRITZ!Box Support"
Disable Hardware acceleration
I'm running CentOS 7 in a Google Compute Engine VM, and trying to connect to it via Chrome Remote Desktop. When I run the start-host command, it fails with "OAuth error" and no more information.
I accessed the https://remotedesktop.google.com/headless site with Chrome, filled out the choices, and went through the authorization phase. There was not an option for CentOS, so I chose "Debian" and when it gave me the connect command, I replaced the path to start-host with the CentOS one of /usr/lib64/chrome-remote-desktop/start-host, and running the resulting command fails.
I did the likely web searches and found some fairly old and unhelpful information, but nothing useful.
If I can't get Chrome Remote Desktop working, I'd be willing to try another method to run GUI-based applications (in this case, IBM's oneWEX). I can get X11 to sort-of work remotely, but not well enough to run oneWEX.
This is the command I got from the Chrome site, modified to work with CentOS:
DISPLAY= /usr/lib64/chrome-remote-desktop/start-host --code="<code>" --redirect-url="https://remotedesktop.google.com/_/oauthredirect" --name=
The start-host command asked the expected questions of the computer name and PIN, then gave the error:
Couldn't start host: OAuth error.
When you get the code from https://remotedesktop.google.com/headless it is only good for a few minutes, and only one time use.
Just go back to https://remotedesktop.google.com/headless follow the prompts and get a new code for every attempt.
In my case, I got another error when I first ran the command. I tried to resolve it, and reran the same command (with the original code). I kept getting the "Couldn't start host: OAuth error." until I figured out I needed to get a new code from https://remotedesktop.google.com/headless for each attempt.
FYI: The error message is not given right away, but after entering the computer name and double entering the pin.
According to https://bugs.chromium.org/p/chromium/issues/detail?id=1039016, this could apparently also happen if the /usr/lib64/chrome-remote-desktop/start-host binary is not one from the "official" DEBian package built and distributed by Google, but one built from source e.g. by yourself or your Linux distribution (such as the chrome-remote-desktop package built by Fedora; https://bugzilla.redhat.com/show_bug.cgi?id=1788448 aims to clarify how to use that one).
What I can see here is that you previously added some libraries to your CentOS instance, I tried replicating the error myself and inside my CentOS 7 instance (from Compute Engine) I don't seem to have any /usr/lib64/chrome-remote-desktop/ folder.
Or is it from your local machine?
I had the same error and found that refreshing the headless page to get a new code string in the command worked.
I have installed and pulled from docker.io successfully many times on Redhat Enterprise Linux. But now I am having a very difficult time with a slightly different environment behind a proxy server.
I am starting to think there is a modification Redhat has done to the docker packages preventing my proxy setting from working correctly. When I try to do a simple "docker pull centos", I get the frustrating error: "Tag latest not found in repository docker.io/library/centos". I have tried other tags as well with no luck. Before I put the proxy setting in, I received "authorizationrequired" messages. I got past that by adding the proxy info to /etc/sysconfig/docker. Then I received x509 errors. I got past that by adding the appropriate certificate file to docker. Now, with everything seemingly correct, I am unable to do a simple pull. From what I can tell, this is not an issue with stock docker. Is there something else that needs to be done to make the redhat docker package work with a proxy? Any help is greatly appreciated. I tried everything in another stackoverflow question to no avail.
Everything looked like it was working from the cli. However, I ran /var/log/messages | grep docker to look at the docker daemon logs. I was still getting certificate errors. I loaded hub.docker.com into my browser and extracted the certificate chain. I put those in /etc/docker/certs.d/docker.io and it worked part-way.
I needed to add those proxy certs to the global location and now it works all the way.
Running HHVM's hh_server tool in Docker fails with following error:
Fatal error: exception Not_found.
Same tool works fine in the host with same OS (Ubuntu 14.04) and HTTP server (nginx).
Any idea how this might occur?
I had the exact same problem on a Debian image. After talking to a guy at hhvm's IRC channel I got it working by setting the USER environment variable to a username. Apparently hh_server don't work if USER is empty