0.94 "stat /usr/local/Repetier-Server/bin/RepetierServer: no such file or directory"

Hi there, 
I use the folowing dockerfile to run a secondary repetier server on a amd64 infrastructure. Worked fine since 0.86 but after switching to 0.94 it cannot find the /usr/local/Repetier-Server/bin/RepetierServer file anymore. I have found a arm related post regarding this, but that does not seem to help me with 64bit AMD:

RUN wget --output-document repetier-server.deb -q http://download.repetier.com/files/server/debian-amd64/Repetier-Server-0.94.1-Linux.deb \
&& dpkg --unpack repetier-server.deb \
&& rm -f repetier-server.deb \
# We do this to avoid failing on service installation.
&& rm -f /var/lib/dpkg/info/repetier-server.postinst \
&& apt-get -qqf install
RUN adduser --quiet --home /var/lib/Repetier-Server --system --disabled-login --ingroup dialout repetierserver \
&& adduser repetierserver tty
RUN rm -rf /var/lib/Repetier-Server \
&& ln -sf /data /var/lib/Repetier-Server
VOLUME "/data"
EXPOSE 3344
USER repetierserver
CMD [ "/usr/local/Repetier-Server/bin/RepetierServer", "-c", "/usr/local/Repetier-Server/etc/RepetierServer.xml" ]

The Container will not start then:

docker logs repetierserver-1
container_linux.go:265: starting container process caused "exec: \"/usr/local/Repetier-Server/bin/RepetierServer\": stat /usr/local/Repetier-Server/bin/RepetierServer: no such file or directory"

Any ideas? 

Danke!

Comments

  • Just installed it on a plain amd64 linux and the file was there.  We have modified postinst to do some more checks but I see you delete it anyway so that should not be the problem.

    Have you tried calling something else as CMD and login with bash to see if the files are really not there or just have wrong permission?

    BTW: How do you see the serial devices? Or is /dev automatically shared with docker images?

  • If I just sleep as CMD I see there is no /user/local/Repetier-Server folder at all. 

    during image build it seems that it immediately gets uninstalled again ( see last two lines ):
    Step 3/9 : RUN wget --output-document repetier-server.deb -q http://download.repetier.com/files/server/debian-amd64/Repetier-Server-0.94.1-Linux.deb  && dpkg --unpack repetier-server.deb  && rm -f repetier-server.deb  && rm -f /var/lib/dpkg/info/repetier-server.postinst  && apt-get -qqf install
     ---> Running in 283eb8b917b6
    Selecting previously unselected package repetier-server.
    (Reading database ... 7303 files and directories currently installed.)
    Preparing to unpack repetier-server.deb ...
    Unpacking repetier-server (0.94.1) ...
    (Reading database ... 
    (Reading database ... 5%
    (Reading database ... 10%
    (Reading database ... 15%
    (Reading database ... 20%
    (Reading database ... 25%
    (Reading database ... 30%
    (Reading database ... 35%
    (Reading database ... 40%
    (Reading database ... 45%
    (Reading database ... 50%
    (Reading database ... 55%
    (Reading database ... 60%
    (Reading database ... 65%
    (Reading database ... 70%
    (Reading database ... 75%
    (Reading database ... 80%
    (Reading database ... 85%
    (Reading database ... 90%
    (Reading database ... 95%
    (Reading database ... 100%
    (Reading database ... 11495 files and directories currently installed.)
    Removing repetier-server (0.94.1) ...
    dpkg: warning: while removing repetier-server, directory '/usr/local' not empty so not removed
  • ok I figured it our. apt was too quite with the -qq params :) 

    seems like there is a new dependency to libusb-1.0-0 that was not met. Therefore it did not install properly. 

    So adding this worked fine:
     && apt-get update \ && apt-get -y install libusb-1.0-0
  • I see. Yes the firmware uploader depend on that.
Sign In or Register to comment.