I have Docker Desktop on Windows 10 and I run Apache NiFi 1.19 within container.
NiFi keeps restarting, by itself, without giving any useful log message, exception message, or whatever I can trace back with.
Any ideas what can be going wrong? I have tried many things.. including this, but nothing helped out.
Ok, finally, so the problem was built-in Hyper-V backend of the Docker (i.e. the default VM environment that comes with Docker Desktop).
I just opted for Use the WSL 2 based engine choice and problem went away.
From the Docker Desktop dashboard, go to settings and in the General tab, select "Use the WSL 2 based enginge":
It's been quite a while that I am struggling to solve an issue but no success. I would like to run Carla simulator 9.10.1 in their provided docker container on a headless (without display) cluster which is managed by Slurm. We use enroot containers on our cluster. So, we convert docker images to enroot sqsh files first, and then we run it. Carla runs flawlessly when a display is connected with or without a container on my PC. However, when it comes to running it on a headless cluster, non of the official Carla methods for running it on a headless cluster worked for me because I am only able to run my experiments inside an enroot container with Slurm (not on the head node) on a headless cluster. So, there are some permission restrictions for my user as well on the cluster. I have to mention that I only need to run Carla and I don't want to see the GUI but the problem is Carla doesn't start off-screen or without rendering. The app quits without any error when I also run it with Off-screen or no-rendering flags. So, I was wondering
if it is possible at all to run a GUI app inside a container on a headless cluster?
I have tried creating a virtual display but when I'd like to run Xorg :7, I get (EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied). I have also set allowed_users=console to /etc/X11/Xwrapper.config file but it didn't help. Is there any other way to create a virtual display?
I have not tried xvbf because Carla needs OpenGL and people say it may not be easy to make it work.
Is there any way to get this working? Thanks.
you can try virtualgl but it only works if you don't need to see the display itself.
wget https://sourceforge.net/projects/virtualgl/files/3.0.1/virtualgl_3.0.1_amd64.deb
dpkg -i virtualgl_3.0.1_amd64.deb
apt-get update
apt-get -f install
after installing you can use
vglrun glxgears
where glxgears is your application.
I have installed Docker Edge 18.06.01-ce on Microsoft Windows 10 with Fall Creators Update.
I want to find a way to configure Docker silently - from for example command console. Unfortunately, I can't use Docker features without Docker daemon running in the background.
Normally I would open Docker for Windows.exe- it does manage Hyper-V machine MobyLinuxVM, creates network switches etc. The problem is that this application is running in tray and has GUI.
Is there any way to start this application from command console and wait until it will configure everyting (until Docker will work correctly)? I have already tried creating manually new machine and starting Docker service, but it does not work - I suspect that I need to map new machine somehow to new console windows (docker-machine env?).
I have the latest Docker for Mac installed, and I'm running into a problem where it appears that docker-compose up is stuck in a Downloading state for one of the containers:
± |master ✗| → docker-compose up --build
Pulling container (repo.io/company/container:prod)...
prod: Pulling from company/container
somehash: Already exists
somehash: Already exists
somehash: Already exists
somehash: Already exists
somehash: Pulling fs layer
somehash: Already exists
somehash: Already exists
somehash: Downloading [=================================================> ] 234.6 MB/239.3 MB
somehash: Download complete
somehash: Download complete
^^ this is literally what it looks like on my command line. Stopping and starting hasn't helped, it immediately outputs this same output.
I've tried to rm the container but I guess it doesn't yet exist, it returns the output No stopped containers. --force-recreate also gets stuck in the same place. And perhaps I'm not googling for the right terminology but I haven't found anything useful to try - any pointers?
I just needed to restart Docker.
Linux users can use sudo service docker restart.
Docker for Mac has a handy button for this in the Docker widget in the macOS toolbar:
If you happen to be using Docker Toolkit try docker-machine restart.
I faced the same problem! Restarting the service didn't help, downloading again didn't help. It used to get stuck at random instances leaving me with no option but to kill the pull request.
One thing which worked for me was to download 1 file at a time. For Ubuntu users, you can use the following steps:
Stop the service:
sudo service docker stop
Start docker with max concurrent download set as 1:
sudo dockerd --max-concurrent-downloads 1
Download the required image:
sudo docker pull <image_name>
Download images, after that stop the terminal and start the daemon again as it was earlier.
sudo service docker start
I had the similar situation this morning where my network suddenly went down and I was forced to power cycle the modern, while docker-compose was still in the middle of downloading stuff from docker hub.
Yes, bouncing the docker daemon process seems to resolve this.
For Linux users - do sudo service docker restart to fix it.
Go to the Docker Preferences from its menu bar icon. Within there is a "bug" icon. Click on that and then "clean / Purge data"
I'm running OSX and restarting Docker for Mac didn't help. Neither did a full restart or upgrading VirtualBox. What did work was turning my wifi interface on and off every time it got stuck. I had to do this repeatedly, but it eventually downloaded the entire image.
Directly download the necessary images using docker, e.g.
docker pull company/container
and then run
docker-compose up
again. Worked for me on MacOS.
I found a possible workaround.
I have my docker engine installed in a Ubuntu 18.04 Snap Environment.
I discovered searching in some forums that users relate this behaviors to limitation in the download bandwith.
So in the picture below you are going to watch that the components was stucked
Part of the Downloads stucked and finally I cancelled the process CTRL + C
I added two parameters or flags in the configuration file that controls the docker daemon behavior: max-concurrent-downloads 1 and max-concurrent-uploads 1
In my case remember, i am working in a snap environment. This file is located in this directory: /var/lib/docker/current/config/daemon.json
REMEMBER TO STOP ALL DOCKER PROCESS BEFORE THE FILE MODIFICATION, AND CREATE BACKUP OF THE FILE
Add the two lines in the picture. This is going to help you to limit the downloads to only one by one
This is the process that helped me to resolve this problem.
Download Succesfull
I had this issue in my VirtualBox when doing a docker pull on the image but it got stuck at a specific position and never moved from there. So, the issue was due to the network adapters in my VM. I was using NAT by default. When I switched it to "Bridged adapter", the issue went away.
I had a similar problem on docker for windows for a couple of days and when I tried to connect to the virtual machine (via Hyper-V Manager) the downloads started speeding along. I have no idea why but it worked for me...
Completely remove docker
Install docker again
It should work now
I tried to restar docker, update docker, but didnt help
on linux machine, or when I connect to boot2docker VM using putty, I can see this nice progress indicator when I'm pulling images:
1491ff176f58: Downloading [===========================> ] 1.481 GB/2.721 GB
Unfortunately when pulling exactly the same image from Git Bash (MinTTY) on Windows
git version 2.5.3.windows.1
docker version:
Client/Server: 1.8.2
There is no progress bar.
Any idea why?
Docker Toolbox 1.8.3+ has workaround for this issue:
NOTE: When using interactive commands, prepend winpty. Examples: 'winpty docker run -it ...', 'winpty docker exec -it ...'.
See:
https://github.com/docker/toolbox/blob/v1.8.3/windows/start.sh
For me it renders the progress bar, but it prints each state of progress bar as new line (not replacing lines like in ssh session).
UPD:
In Docker Toolbox v1.9.0c this issue has been fixed:
On Windows, use bash and the default terminal for the Docker
Quickstart Terminal instead of mintty. This fixes several bugs causing
cannot enable tty mode on non tty input or repository name component
must match "a-z0-9(?:[._]a-z0-9)*".
Some servers are providing info about the full size of the downloaded file. In this case you get a progress bar. Some servers are just streaming this data without size info, in this case docker can't show the data.
This is not a bug, this is a feature :) :)