I am facing a problem when trying to run inside an interactive command prompt Sigcheck.exe from Sysinternals.
It starts running and shows the banner info like copyright but it looks like it's blocked, it just stays in running state without going further.
I tried running it on my laptop just to show the help and it works.
However, in docker it stops.
Does anyone know what might be the cause?
Add the /accepteula command line parameter
Related
I've tried installing Docker and so far I've never been able to use it on my Ubuntu machine:
when I try to start Docker Desktop it only shows Docker Desktop stopped... for an indefinite amount of time. There sometimes shows up randomly an Alert with the messages "Unable to calculate image disk size" for a second or so, but it doesn't really help me at all. I'm also not Using Docker very often so I have only a little experience with it.
At this point Docker is always the first program that shows up automatically when I boot up my computer. and it instantly goes to the message: "Docker Desktop stopped..." when I click on the bug Icon I already tried the oprions "Restart", "Clean/Purge data" and "Reset to factory defaults" but none of those options helped me so far. I also can't access the Settings page it only shows a loading animation when I try to open it.
I have the same problem. The only solution I found is to reinstall docker every time I log in. It seems to work fine until I restart the computer.
It is a very bad solution but it's the best that I've got so far.
I have a docker image with a medical data analysis app installed in it. The app works from both gui and console. Normally, in my linux, I run the app from the terminal as
./dsi_studio --action=trk ...
and it works quite smoothly. If you click on this app, it'll try to open a GUI. While I'm trying to use this inside the docker image, it tries to connect to the display in any case (even if I run as shown in the terminal). And, of course, since I didn't do any setup for showing GUI from docker, I get the following error, stating that it couldn't find a display to connect.
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
I don't know why the app is trying to open a display while running in terminal, because it doesn't open a GUI in my linux. I just want to suppress this warning somehow, as if there is a fake display. I don't want to connect my display to docker image, because this image is going to run in batch in an HPC.
So, How can I do this?
You should probably export the DISPLAY environment variable to point to your linux terminal.
Just to test, run
xhost +
in your linux terminal and add
-e DISPLAY=:0.0
to your docker command line
I have some trouble when running gdb in a docker image and I am not sure what is causing the problems since I am a complete newbie when it comes to gdb and docker.
Background
I am trying to write a c++ program for the Lego EV3 which runs on ev3dev. In order to compile it, I have set up docker with the ev3dev image on my Windows machine and am able to successfully build inside that image, transfer the binary to the EV3 and execute it there. This all works well until I need to start (remote) debugging. My plan is to start a gdbserver on the EV3 with the program and the open a gdb session inside the docker container in my Windows machine and connect to the EV3 gdbserver. After I have fixed the first error when remote debugging - I needed to use gdb-multiarch on my Windows machine - I have encountered more problems which I don't really find a solution too.
Problem
When running gdb directly on my Windows machine inside the docker container (or when connecting to the gdbserver from docker using gdb-multiarch) I always get the following output after starting the program with run:
(gdb) run
Starting program: /src/ev3/build/src/EV3_main
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
Warning:
Cannot insert breakpoint -1.
Cannot access memory at address 0x4f58
and when using next or step I get:
(gdb) next
Cannot find bounds of current function
Since I couldn't really find any solution online, I would really appreciate any help!
Thanks in advance!
I always get the following output after starting the program with run
This error usually means that the dynamic loader in your docker container has been fully stripped. It's a packaging mistake by the creator of that container.
If you are not using dlopen(), this isn't a big problem.
(gdb) next
Don't do that: you are not stopped in a location where GDB knows where the next line is. Do continue instead.
I'm using Docker on Itellij ultimate on Windows 10 home, however I met this problem when using command docker ps. Can any one tell me how to solve this problem?
docker_engine: The system cannot find the file specified is a general connectivity error to the service. Most likely related to the desktop app not being running. So make sure it's in the tray icon up and running, otherwise restart it. Otherwise, check the firewall and antivirus for any block rules.
I installed WinDDK 7600 in my Windows XP operating system.Now,when I double click the devcon.exe(Location- D:\WinDDK\7600.16385.1\tools\devcon\i386),the command prompt is just showing up and suddenly disappears.Can anyone resolve this issue.
As far as I'm aware devcon is a command-line only program. You have to run it from a command window (cmd.exe) with the appropriate parameters. Once you know the parameters you want to use, you can write a batch file to easily recreate the command you want.
I ran across this post because Win7 has a similar problem even when running in cmd.exe.
There is a solution found on Microsofts website here:
http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/devcon-not-working-correctly-in-windows-7/9abcc12c-d7db-4249-aec4-fc4ff0ea6ee8
I have not been able to verify it yet.
The same (a windows open and automatically close) happens even if using a normal command prompt. However opening the command prompt with administrator rights and then run devcon works.