-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] fail to start at host network mode #28
Comments
Do you have the same crash when you execute:
|
Also, could you provide the output of:
|
yes, same crash. |
If the container cannot be started successfully, will the command |
Yes, the command is executed in a new temporary container instance. |
I tried your command, but there's no output(a pause, and then returned to the command prompt.). I also tried to use "docker ps -a --latest", but there was no container-id found. If I use this: docker run --rm --network host jlesage/czkawka, there would be ouput just as similar as I submitted. |
Do you have an X server running on the host ? |
Sure, actually I'd tried the same command(sudo netstat -x|grep X11-unix) on my host at the same time when I executed it on the container. There was no X11 on my host which is a NAS (Synology 918), and the system is called DSM which is based on web rather than X11, so no output was generated. |
Current Behavior
I used this docker on my Synology 918 (DSM7)
There’s no problem if I started it with port mapping, like 5800:5800, however if I started the docker in host network mode, it reported the below log:
Log:
[app ] 06:51:38.237 [INFO] czkawka_gui: Set thread number to 2
[app ] (czkawka_gui:630): Gdk-WARNING **: 14:51:38.561: The program 'czkawka_gui' received an X Window System error.
[app ] This probably reflects a bug in the program.
[app ] The error was 'BadShmSeg (invalid shared segment parameter)'.
[app ] (Details: serial 1230 error_code 128 request_code 130 (MIT-SHM) minor_code 3)
[app ] (Note to programmers: normally, X errors are reported asynchronously;
[app ] that is, you will receive the error a while after causing it.
[app ] To debug your program, run it with the GDK_SYNCHRONIZE environment
[app ] variable to change this behavior. You can then get a meaningful
[app ] backtrace from your debugger if you break on the gdk_x_error() function.)
Expected Behavior
No response
Steps To Reproduce
No response
Environment
Container creation
It only has problems at host network mode.
Container log
Container inspect
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: