# Docker Container Cannot Run the QT Application for Multiple Times

XMLWordPrintable

#### Details

• Type: Story
• Status: Done
• Resolution: Done
• Fix Version/s: None
• Component/s:
• Labels:
• Story Points:
0
• Sprint:
TSSW Sprint - Oct 10 - Oct 24
• Team:
Telescope and Site
• Urgent?:
No

#### Description

Docker container cannot run the QT application for multiple times. The image is the latest lsstts/develop-env:develop. The image ID is 4640911798ae. This does not happen for the docker image at three weeks ago.

I used the CentOS 7 as my host machine to run the docker container. The container can run the first several times for the QT application. However, after waiting for some time and rerun the QT application, it will fail.

When the error happens, I have:

 current_tai uses current_tai_from_utc; clock_gettime(CLOCK_TAI) is off by 37.0 seconds qasync: QT_API not set, defaulting to PySide2. qt.qpa.xcb: could not connect to display :0 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.   Available platform plugins are: eglfs, minimal, minimalegl, offscreen, vnc, webgl, xcb.   Aborted (core dumped) 

After this error happens, I exited the container and ran a new container. But the QT application can not run anymore as the above error message. I need to reboot my host machine to rerun the QT application.

Note:
1. After some debugging in my side, I do not see the above error if I do not use the root to enter the container (usually I do this for the control ability in CentOS host machine; MAC OS will do the file permission for you). I will continually investigate this.
2. After using the container, the host machine can not run the labview anymore. Need to reboot the host machine. In this reboot, the "restart" is useless. I would need to showdown the host machine with power cycle to solve this issue. This is weird.
3. Sometimes, this docker can crash the X11 in MacOS. This never happened before.
4. The docker file is here: https://github.com/lsst-ts/ts_cycle_build/blob/main/build/develop-env/develop-env/Dockerfile

#### Activity

Hide
Te-Wei Tsai added a comment -

I used the latest developer docker image: 30ef926d07c3 and I could not reproduce the error after 2 hours trying.

Show
Te-Wei Tsai added a comment - I used the latest developer docker image: 30ef926d07c3 and I could not reproduce the error after 2 hours trying.
Hide
Te-Wei Tsai added a comment -

Please see the comment. I do not know why.

Show
Te-Wei Tsai added a comment - Please see the comment. I do not know why.
Hide
Wouter van Reeven added a comment -

Thanks for spending time on trying to reproduce this and sorry for not succeeding.

Show
Wouter van Reeven added a comment - Thanks for spending time on trying to reproduce this and sorry for not succeeding.

#### People

Assignee:
Te-Wei Tsai
Reporter:
Te-Wei Tsai
Reviewers:
Wouter van Reeven
Watchers:
Te-Wei Tsai, Tiago Ribeiro, Wouter van Reeven