I’m training at selenium and docker right now. For this I created a project by following this tutorial that explains how to set up a selenium grid with docker compose.
https://www.youtube.com/watch?v=NjQ5zZM7fpI
I also went to the docker-selenium repository and used the following yml file:
https://github.com/SeleniumHQ/docker-selenium/blob/trunk/docker-compose-v3.yml
The grid is correctly configured when I navigate to:
http://localhost:4444/ui/index.html#/
The 3 nodes appear in the hub. However I do not know how to get the ui of docker which is shown in the tutorial where we see the images of the containers.
Here's a screenshot:
I’m a little ashamed to ask this question but I looked for a moment and I discovered docker since this morning...
How do I get this interface ?
My configuration:
-Linux Ubuntu 20.04
-Google and chrome 95
-the last version selenium server : 4.1.1
-a docker account
Thanks
Related
I've a Symfony project that I am running on my PC with Symfony serve.
This project is on Bitbucket that has IP restrictions, I can only work from home and nowhere else for security reasons, and all works just fine :).
I wanted to create a Docker image so that I can easily change my machine and be able to deploy it elsewhere.
So I created a Docker image and did the necesseray configurations and all seems good, I can open the project and work the same way as before. The Docker has the default WSL (WSL1) and I've noticed that the application isn't running as fast as usual (outside the Docker, to load a page it would take 3 seconds, while with Docker it takes at least 30 seconds).
I did some research and found out that I could use the WSL2 with DOCKER which provides better performance than the legacy Hyper-V Backend and Enabled integration for the distro UBUNTU-20.4. The problem using the WSL2 is that I am no longer able to pull my project in the WSL2 (from the Ubuntu-20.0) because of the IP restrictions.
It is really strange that I cannot find any configuration for this and I have no idea what should I do to change it. If I pull the project outside the WLS2 distro it works, with the default WSL it works also but not with the WSL2.
I removed the IP restrcitions and the Docker image worked fine, I have the same speed as If I was outside the Docker. The only problem is that I cannot use the IP restrcitoins for this !
Does anyone know how to fix this ? I haven't been able to find any documentation for this issue.
I am using Windows 10 and the Docker version : 4.5.1 (74721)
Thanks a lot for any information.
I'm developing an python-django app running in docker containers (django, celery, postgres, redist...etc). It runs on Windows 10 with WSL2-Debian & Docker Desktop.
During my work I need to observe the consoles of all those containers, so I can monitor apps behavior, like when you run docker-compose up so you got all of them live.
When you click on the container within windowed Docker Desktop app you can see the container's console output, but not actual - it looks like it works until some point of time and there are no updates of the consoles output.
I remember it was working live just prior to a two or three Docker Desktop updates, and I'm sure it was real time there, but not now.
Did I change a setting or Docker Desktop was bugged?
PS. When I start my containers with docker-compose up (without -d) I can observe live logs on my shell console, but not in Docker Desktop anymore.
Any help how to restore Docker Desktop live console view?
The Docker Desktop 3.4 (released June 9th, yesterday) is supposed to have resolved docker/for-win issue 11251.
I don't see the error after upgrading (with the normal docker-compose, not the beta docker-compose v2).
However, as commented by the OP twk and in issue 11251:
the live log is somehow broken - extra newline is added after every new line, but historical log entries (Eg. when you switch to/from another container) are displayed without newlines between entries (which is OK).
Update June 29th from Mathieu Champlon
Sorry it took a while but we now have an internal build that should fix it, if you wanted to give it a try:
win/stable/amd64/66242/Docker Desktop Installer.exe
Update Aug. 2021: Issue 11251 just closed with:
Docker Desktop 3.6.0 has been released containing a fix for this issue.
It's a bug in Docker Desktop v3.3.3
GitHub issue: https://github.com/docker/for-win/issues/11251 as pointed by #Drarig29
I am using VS2019 with docker support (and windows docker running). When creating a console app there is no checkbox for docker support like there is for a dotnetcore web app. This means i cannot publish a container to ACR from VS2019.
I can create a console app and then add docker support and i can build image but embarrassing enough i cannot locate the image that's built or figure how to get it into ACR. running docker ps -a shows nothing in the container list.
So: is there support for pushing containers to ACR from VS2019 console apps?
If not then exactly how do i build a docker image of a console app and get it to ACR - am i left with CLI only?
thanks
Paul
I managed to solve this.
The issue was that the underlying version of windows 10 i was on would not allow me to create a docker image using a more modern supported version of windows nano server. Once i updated windows and double checked the base image that create image was using it would all work. Take the resulting docker image and use the azure cli to push to ACR and then i can run the container from ACI...
Bit tortuous compared to creating a web app but it worked...
I am trying to run Cosmos DB emulator in a docker container. My OS is Windows 10.
I followed all the steps as explained by Microsoft here
Eventually, after importing the certificate the Enulator generates etc. I do manage to have a container running, but the UI looks empty (see below):
My understanding is that the UI should look like this instead:
This second UI is the one I can see running the emulator directly on my machine (no docker container involved)
Notice how the UI in the docker container says "Document DB", while the one running on my machine says "Cosmos DB". Not to mention the different layout (and the fact that the second one actually works)
What puzzles me is that I am certain this is the same installer we are looking at here. I know this because, after having this issue with the official Microsoft image, we build our own docker image using the same installer that put Cosmos DB Emulator on our machines and when we run it... same result.
To be clear - those 2 UIs are the result of the same installer, running in docker container and running on a windows 10 machine.
Has anyone else encountered the same issue and if so, have you found a way to fix this issue?
All help highly appreciated
I want to run Cloudera using a Docker image (specifically, the cloudera/quickstart image).
However, on Docker Hub I can only find beta versions:
https://hub.docker.com/r/cloudera/quickstart/tags/
What's the correct way of getting a more up-to-date image?
Should I just download a beta image and then install parcels? Would I do that using Docker Compose? If so, can I find instructions for that online?
Or is there a completely different way to solve this?
To run Cloudera Quickstart within Docker, follow the instructions on that page:
https://www.cloudera.com/documentation/enterprise/latest/topics/quickstart_docker_container.html
Forget about your concerns regarding the "beta" tag. These tags are there, because the Docker image of Cloudera Quickstart is in beta mode. However, the CDH version in there is not.
You will find this out on your own, once you run the container and check the CDH version inside.