bigtractor

[bigtractor]

There was another stealthy update on the docker page the day of my last comment.  Although the instructions themselves just say to run docker normally, there is now a new comment at the very end saying to run it in privileged mode.  This seems to work, though I can’t understand why NoMachine needs privileged mode.

Happy to have things working, but little concerned about the stealth updates.  They were clearly done in response to this thread, but no comment made here to help me out.  I had planned to buy workstation packs for our devs, but worried about the quality of support now.

[bigtractor]

Thanks for your suggestion.  It’s not clear whether the AppArmour tips are intended to be run on the host or the docker container, but since I am testing on OS X I ran them in the docker container with no effect.  The error is still there in nxerror.log

Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

I noticed that the docker knowledgebase article you linked to had been updated since I opened this thread, so I tried following the dockerfile and run script exactly, updating only the version and md5 variables.  Unfortunately it still fails in the exactly the same way as with my own dockerfile.

Assuming your knowledgebase article has been tested, I can’t understand why it’s not working for me when followed exactly.

[bigtractor]

I can’t upload the attachments (“Upload Errors: Sorry, this file type is not permitted for security reasons.”).  So here’s the text:

DockerFile

FROM ubuntu:xenial

ENV DEBIAN_FRONTEND noninteractive

RUN apt update \
&&  apt -y upgrade \
&&  apt install -y –no-install-recommends \
curl \
sudo \
openssh-server \
lxde \
&&  rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*

RUN useradd –create-home –shell /bin/bash user \
&&  adduser user sudo

RUN curl -L http://download.nomachine.com/download/5.1/Linux/nomachine_5.1.54_1_amd64.deb -o /tmp/nomachine.deb \
&&  dpkg –install /tmp/nomachine.deb \
&&  rm /tmp/*.deb \
&&  apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*

RUN mkdir -p /var/run/sshd \
&&  sed -i “s/.*PasswordAuthentication.*/PasswordAuthentication yes/g” /etc/ssh/sshd_config \
&&  sed -i “s/.*UsePAM.*/UsePAM yes/g” /etc/ssh/sshd_config

COPY run.sh /run.sh
RUN chmod +x run.sh

EXPOSE 22 4000 4848

CMD [“/run.sh”]

Run.sh

#!/bin/bash

PASS=${PASS:-$(pwgen -s 6 1)}
echo “user:$PASS” | chpasswd

/etc/NX/nxserver –startup
tail -f /usr/NX/var/log/nxserver.log

Digging deeper, I found this in the nxerror.log

2645 2645 11:12:37 718.294 NXDBusConnect: ERROR! Connection failed: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

Does this mean NoMachine can’t run in Docker any longer due to issues with DBus?

 

Thanks

[Author]

Posts