![]() ![]() # It may happen that the CUPS service will be activated again after reboot, because it's required by another service, to check this ![]() # Furthermore, you may want to disable the CUPS service # If port 631 is in use, it's highly likely that the CUPS service is running, then check the service status ![]() ![]() # Check if a specific port is in use on the host machine (e.g. Port conflict: in case any required port on the host machine is already in use, Docker will fail to bind the container port to the host port, when this happens, you'll find a line in /var/log/cups/error_log: Unable to open listen socket for address 0.0.0.0:631 - Address already in use. Please be aware, the host networking driver only works on Linux hosts, and is not supported on Docker Desktop for Mac, Docker Desktop for Windows, as stated here. For more information about Docker's network, please check here and here. However, the dbus service is still needed on the host machine (to check its status, you can run for example systemctl status dbus on Ubuntu), and even it is deactivated, it would be automatically triggered to active when avahi-daemon starts running. And in this way, we don't require dbus (a simple interprocess messaging system) package in the container. When using host network mode, it would discard published ports, thus we don't need to publish any port with the run command (e.g.: -p 631:631 -p 5353:5353/udp). Network: With the option -network=host set, the container will use the Docker host network stack. Sed -i.bak "s/FROM arm32v7/ubuntu:/FROM ubuntu:/ " Dockerfile & rm Dockerfile.bak # Change base image to x86_64 architecture Sed -i.bak "s/FROM ubuntu:/FROM arm32v7/ubuntu:/ " Dockerfile & rm Dockerfile.bak # Change base image to ARMv7 architecture ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |