You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I needed to be able to dockerise the application to run Windows, Mac, and Linux to test some print applications and server listeners we built. But the docker build and run kept failing.
The list of errors I encounter:
Dockerfile COPY from windows to the image would make bash files fails as dos files are CRLF and unix expects LF.
Dockerfile COPY needed to be followed by a chmod statement to make the appropriate files executable
During the make process compiling with the necessary avahi libs kepy failing
Docker on windows via WSL2 has really frustrating errors with systemd even with it enabled leading to issues with avahi-daemon and service management
The ippserver is unuseable without port forwarding
Describe the solution you'd like
An updated Dockerfile with compatibility for Docker on windows via WSL2
use sed to remove the carraige return and using chmod to make the appropriate files as executable
WORKDIR /root/ippsample
RUN find . -type f \( -name "config*" -o -name "install-sh*"\) -exec sed -i 's/\r$//' {} \;RUN find . -type f \( -name "config*" -o -name "install-sh*"\) -exec chmod +x {} \;
added libavahi-core-dev to list of packages
RUN apt-get install -y mdns-scan libavahi-core-dev
manually starting the avahi-daemon due to systemd issues
# Create entrypoint.sh script to start dbus and avahi-daemonRUN echo '#!/bin/bash\n\service dbus start\n\avahi-daemon --no-chroot -D\n\$*\n\
run call to enable port forwarding, adding -p 0.0.0.0:631:631
Can you attach your complete Dockerfile to this issue? I don't see any particular issues with adopting those changes but the current Dockerfile tries to optimize the size of the resulting image by splitting the build from the container image, so there are multiple places where we are running apt-get for example...
Can you attach your complete Dockerfile to this issue? I don't see any particular issues with adopting those changes but the current Dockerfile tries to optimize the size of the resulting image by splitting the build from the container image, so there are multiple places where we are running apt-get for example...
Thanks!
Hey man, no problem.
Im still working on this, will keep you posted on anything else I find and anything I might be able to improve. BTW I was considering changing build system for windows, because of the issues in VS2019. I think it has issues with the compiler version interpreting functions and function declarations. (just spit balling here)
Is your feature request related to a problem? Please describe.
I needed to be able to dockerise the application to run Windows, Mac, and Linux to test some print applications and server listeners we built. But the docker build and run kept failing.
The list of errors I encounter:
Describe the solution you'd like
An updated Dockerfile with compatibility for Docker on windows via WSL2
RUN apt-get install -y mdns-scan libavahi-core-dev
Additional context
I fully acknowledge that there might be a more appropriate way to do this.
The text was updated successfully, but these errors were encountered: