NXFrameBuffer failed to start in Docker

[k.gorbachev]

Hello, I am trying to start NX server inside the docker container, how it is described in https://knowledgebase.nomachine.com/DT11R00194 article.
But I have an error during connection to NX-server. There are Docker logs:

NX> 111 New connections to NoMachine server are enabled.
NX> 161 Enabled service: nxserver.
NX> 162 WARNING: Cannot find X servers running on this machine.
NX> 162 WARNING: A new virtual display will be created on demand.
NX> 161 Enabled service: nxd.
3017 3017 2021-09-24 11:06:20 321.326 NXSERVER Starting LS 7.6.2 and services.
3017 3017 2021-09-24 11:06:20 321.478 NXSERVER System information: Debian GNU/Linux 10 (buster), standalone.
16 16 2021-09-24 11:07:33 185.073 NXSERVER Starting LS 7.6.2 and services.
16 16 2021-09-24 11:07:33 185.178 NXSERVER System information: Debian GNU/Linux 10 (buster), standalone.
57 57 2021-09-24 11:18:30 115.378 NXSERVER User ‘nomachine’ logged in from ‘172.17.0.1’ using authentication method NX-password.
16 16 2021-09-24 11:18:50 879.912 NXSERVER WARNING! Cannot retreive nxnode PID for virtual server C18548A4DB08CE50DD26DD54E015B4A8.
91 91 2021-09-24 11:18:50 880.557 NXSERVER ERROR! Cannot start node to create session
16 16 2021-09-24 11:18:50 881.157 NXSERVER WARNING! Process ‘/usr/NX/bin/nxexec –node –user nomachine –priority realtime –mode 0 –pid 49’ with pid ‘120/120’ finished with exit code 1 after 0,009 seconds.
16 16 2021-09-24 11:18:50 884.278 NXSERVER ERROR! NXFrameBuffer failed to start.
16 16 2021-09-24 11:18:50 884.473 NXSERVER ERROR! Received error message from nxserver NX> 595 Server could not establish communication with local node.
57 57 2021-09-24 11:18:50 885.316 NXSERVER ERROR! Received error from nxserver –daemon NX> 595 Server could not establish communication with local node.
57 57 2021-09-24 11:18:50 913.435 NXSERVER User ‘nomachine’ from ‘172.17.0.1’ logged out.

[k.gorbachev]

Support team, could you provide some information related to error?

I’ve created repo with demo: https://github.com/slyder/nomachine-in-docker

[Carin]

Hi k.gorbachev,

It looks like this is related to AppArmor. Please take a look at Section 2 -Troubleshooting in this article where we explain how to fix it:  https://knowledgebase.nomachine.com/DT11R00194

 

[k.gorbachev]

@Carin, I’ve checked this article before posting message.

1 I’m using Dockerfile from yours example and it uses debian:buster, not ubuntu which as i understand could have app-armor problem

2 Anyway, i tried to setup app-armor as described in documentation:
root@d8943e1ba353:# apt-get install apparmor-utils
root@d8943e1ba353:# aa-complain /etc/apparmor.d/docker
Profile for /etc/apparmor.d/docker not found, skipping
should i run it on HOST system? I’ve checked system logs and i unable to find any related to permissions logs

3 I’ve checked NoMachine logs and see “Error: Cannot create a new display, please contact your system administrator'”, but why this is happening?

4. is there any tutorial how i could connect NoManiche to already created x11 screen?

[k.gorbachev]

I have added --cap-add=SYS_PTRACE option and it works now. Thanks!

[Carin]

@k.gorbachev You’re welcome! Glad its working now. Thanks for letting us know 🙂

[Author]

Posts