I'm trying to stream docker to my browser (I followed this article). Inside docker I run the chrome browser which is streamed to my Mac browser. The setup using docker is easy, just build the image and run it.
Although the chrome browser is running fine, I can't really visit any pages. As soon as it tries to load a website it displays the following:
(If I visit google.com all works fine btw)
If you would like to reproduce, you can read the article or use this docker image.
Unfortunate, this image does not include chrome, so you have to install it yourself:
$> https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
$> apt-get install -y ./google-chrome-stable_current_amd64.deb
$> google-chrome --no-sandbox
When I replace chrome with Firefox, everything works fine.
Anyway, I hope someone knows how to fix this chrome issue or any suggestion what might be going wrong here would really help!
Related
Windows 10 (19043.1889)
Docker Desktop 4.11.1
I installed docker but it showed "It looks like there is an error with Docker Desktop, restart it to fix it" when opening [Settings] page
I couldn't change any params in [Settings]; I can check some configurations but [Apply & Restart] button didn't enabled.
Several times I tried uninstall & install, but nothing changed.
Docker itself worked, but because of error, I couldn't change resources spec.
I wonder if someone has any idea
Thank you
I installed Lubuntu 19.04 on old Inspiron 6400 computer (GeForce 7300 laptop edition) to teach Scratch to my son through web scratch editor. Every time I open web editor for a new project through firefox, right zone with the cat is blurred and blinks like if video driver was badly configured.
Here is screenshot:
At the beginning I used to have this for the whole Ubuntu system, any application.
Using now Lubuntu, everything seems correct but that srcatch window.
Is it still a video driver issue ? Or is the problem on Scratch application side ?
Edit:
So I revert back to Lubuntu 16.04 to better support GeForce 7300, and eveything gets corrected. Then I upgraded firefox through: sudo apt install firefox. This performed the following:
Start-Date: 2020-03-28 12:06:21
Commandline: apt install firefox
Requested-By: me (1001)
Install: libatomic1:i386 (5.4.0-6ubuntu1~16.04.12, automatic)
Upgrade: cpp-5:i386 (5.3.1-14ubuntu2, 5.4.0-6ubuntu1~16.04.12), libquadmath0:i386 (5.3.1-14ubuntu2, 5.4.0-6ubuntu1~16.04.12), gcc-5-base:i386 (5.3.1-14ubuntu2, 5.4.0-6ubuntu1~16.04.12), libgomp1:i386 (5.3.1-14ubuntu2, 5.4.0-6ubuntu1~16.04.12), firefox:i386 (45.0.2+build1-0ubuntu1, 74.0+build3-0ubuntu0.16.04.1), libstdc++6:i386 (5.3.1-14ubuntu2, 5.4.0-6ubuntu1~16.04.12)
And problem is back again. Any idea ?
Thanks.
I do believe that only some part of the graphics is faulty. Most likely, this is processing and web error. I would recommend checking if you have Adobe Flash and/or Chrome on your computer.
Hopefully this helps.
I'm new to Docker and I'm not very experienced in SSL/certificates etc.
I'm working on a web application that lets the user log in to JIRA via JIRA API to do things. This works on my computer and I don't get any SSL errors. However, when I run it in a Docker container I get
ssl.SSLError: [SSL: WRONG_SIGNATURE_TYPE] wrong signature type error.
My friend ran the exact same Dockerfile in his computer and created a container and it works which is confusing.
I checked the requests library version on my computer and compared it to the one in Docker container but they are the same. What could be the problem? Thank you
Note: I use Windows
Faced similar problem.
Find the solution here
Just to sum up:
There is missing dependencies inside container which your own system already has. You should install them inside docker.
Idk how but pyopenssl library should be install to
So, you need to add:
RUN apt-get update \
&& apt-get install openssl \
&& apt-get install ca-certificates
In your Dockerfile
And add:
pyopenssl==19.1.0
To your requirements.txt
If you don't use requirements.txt just add:
RUN pip install pyopenssl
To your Dockerfile
Hope it'll help
Similar issue happened to me - python tls requests were working fine on my host, but failed with WRONG_SIGNATURE_TYPE once I dockerized my script.
The issue seems to stem from where requests lib uses older TLS stacks with OpenSSL 1.1.1pre9.
I noticed rolling back to python:3.5.3 stopped the error, however for compatibility with newer versions the solution posted in github issue thread worked fine.
i.e. import the TLSAdapter, use it to setup a requests session, then start making requests.
Well, I am not sure where to start.
We have rails based apps.
We did nothing in our websites. (did not touch ANY config file etc).
Just a regular apt-get update, upgrade.
Suddenly 2 websites are down!
What can be the problem?
This is an ubuntu machine that we are running.
DNS is OK.
We can go to the root page that says: ubuntu... everything is working fine.
We have apache server. Tried to: sudo apachectl restart.
Also, working on AMAZON cloud if it matters (aws.amazon)
Tried to reboot from Amazon. Same result.
If anything goes wrong, the first thing you should try is to follow the official troubleshooting guide: https://www.phusionpassenger.com/library/admin/apache/troubleshooting/ruby/
This morning I've started playing with Docker, so installed boot2docker on my Mac.
All seemed to be going well, following the Working with Docker Images documentation until I tried to create a Dockerfile to install the ruby gems.
I spent a long time banging my head against the wall as to why it couldn't connect to install the gems... then I eventually worked it out, so adding this here in case anyone else has this problem in future, as there wasn't anything on Google about it.
Turns out that, because my internet bombed out during the apt-get update command, it didn't complete the update, however running it again, docker was using the cached (incomplete) data, and so if didn't work.
The fix... Run the docker build without the cache using the command...
docker build -no-cache --tag="<vendor>/<build>:<tag>" .