Is there a way to see the display within openshift jupyter-notebook the pod?

[rurusungoa]

When using an openshift container, I would like to create a new project in ocp, create a pod image, and inquire about DISPALY visible in jupyter-notebook within the pod.

When looking at the progress as shown below, it says that "unable to open display":1" " cannot be used when running xhost.

Is it not possible to use display when using jupyter-notebook in an ocp container? Is there any way to take action?

#> echo $DISPLAY
:One

#> xhost
xhost: unable to open display ":1"

I am inquiring because I am using opencv in the project and xhost needs to be "enabled".

1. Error when running jupyter -notebook (python3-ipykernel)

Kernel Restarting
The Kernel for Untitled.ipynb appears to have died. it will restart automatically.

2. Error when going to jupyter-notebook > other > Terminal or pod > details > Terminal

=========================================================
qt.qpa.xcb : could not connect to display :1
qt.qpa.plugin : could not load the Qt playform plugin "xcb" in "/opt/conda/lib/python3.10/site-packages/cv2/qt/plugins" 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 playyform plugins are :xcb
  ========================================================

I am inquiring because the above error occurs because xhost is unable to display. This is something that works well on the server before creating the image.

Since this is a part of the container that should not be imported, I would like to ask if there is anything that needs to be added to “deployment”.

I'm really sorry to bother you, but please reply.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.