How to print from docker container in Openshift Container Platform? [closed]
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I'm trying to print a file from a network printer which is present in my intranet.
I'm able to ping the printer and issue the lp command to print a file.
However the command is saying that it sent the command to print the file. But the printer is not printing the page.
If I try the same command in a Virtual Machine which is in my local machine, I'm able to send the print and the printer is actually printing the page.
I'm able to get same results in both environments except the actual printing is done when I issue command from my local VM.
What is the difference between this OCP environment and my local intranet.
linux debian docker cups printer
asked Nov 26 at 18:09
Tywin Lannister
1
closed as too broad by Rui F Ribeiro, Jeff Schaller, RalfFriedl, Thomas, JigglyNaga Nov 27 at 13:41
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
0
down vote
favorite
I'm trying to print a file from a network printer which is present in my intranet.
I'm able to ping the printer and issue the lp command to print a file.
However the command is saying that it sent the command to print the file. But the printer is not printing the page.
If I try the same command in a Virtual Machine which is in my local machine, I'm able to send the print and the printer is actually printing the page.
I'm able to get same results in both environments except the actual printing is done when I issue command from my local VM.
What is the difference between this OCP environment and my local intranet.
linux debian docker cups printer
asked Nov 26 at 18:09
Tywin Lannister
1
closed as too broad by Rui F Ribeiro, Jeff Schaller, RalfFriedl, Thomas, JigglyNaga Nov 27 at 13:41
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
The VM would have CUPS set up to allow printing. The Docker container probably doesn't have that. You'll either need to set up CUPS inside the Docker container, or permit the container to access the host's CUPS configuration. OCP uses a very restricted configuration for containers by default.
– Haxiel
Nov 27 at 7:42
I was able to add all the printers configuration while building the docker image itself. and I'm able to ping the printers using lpstat command. The thing is if I give print, they're stuck at not-completed state forever. Any way to debug this??
– Tywin Lannister
Nov 27 at 12:07
I'm not too familiar with CUPS itself, so maybe this will help: wiki.debian.org/DissectingandDebuggingtheCUPSPrintingSystem
– Haxiel
Nov 27 at 12:36
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm trying to print a file from a network printer which is present in my intranet.
I'm able to ping the printer and issue the lp command to print a file.
However the command is saying that it sent the command to print the file. But the printer is not printing the page.
If I try the same command in a Virtual Machine which is in my local machine, I'm able to send the print and the printer is actually printing the page.
I'm able to get same results in both environments except the actual printing is done when I issue command from my local VM.
What is the difference between this OCP environment and my local intranet.
linux debian docker cups printer
asked Nov 26 at 18:09
Tywin Lannister
1
I'm trying to print a file from a network printer which is present in my intranet.
I'm able to ping the printer and issue the lp command to print a file.
However the command is saying that it sent the command to print the file. But the printer is not printing the page.
If I try the same command in a Virtual Machine which is in my local machine, I'm able to send the print and the printer is actually printing the page.
I'm able to get same results in both environments except the actual printing is done when I issue command from my local VM.
What is the difference between this OCP environment and my local intranet.
linux debian docker cups printer
linux debian docker cups printer
asked Nov 26 at 18:09
Tywin Lannister
1
asked Nov 26 at 18:09
Tywin Lannister
1
asked Nov 26 at 18:09
Tywin Lannister
1
asked Nov 26 at 18:09
Tywin Lannister
1
asked Nov 26 at 18:09
Tywin Lannister
1
1
closed as too broad by Rui F Ribeiro, Jeff Schaller, RalfFriedl, Thomas, JigglyNaga Nov 27 at 13:41
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as too broad by Rui F Ribeiro, Jeff Schaller, RalfFriedl, Thomas, JigglyNaga Nov 27 at 13:41
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
The VM would have CUPS set up to allow printing. The Docker container probably doesn't have that. You'll either need to set up CUPS inside the Docker container, or permit the container to access the host's CUPS configuration. OCP uses a very restricted configuration for containers by default.
– Haxiel
Nov 27 at 7:42
I was able to add all the printers configuration while building the docker image itself. and I'm able to ping the printers using lpstat command. The thing is if I give print, they're stuck at not-completed state forever. Any way to debug this??
– Tywin Lannister
Nov 27 at 12:07
I'm not too familiar with CUPS itself, so maybe this will help: wiki.debian.org/DissectingandDebuggingtheCUPSPrintingSystem
– Haxiel
Nov 27 at 12:36
add a comment |
The VM would have CUPS set up to allow printing. The Docker container probably doesn't have that. You'll either need to set up CUPS inside the Docker container, or permit the container to access the host's CUPS configuration. OCP uses a very restricted configuration for containers by default.
– Haxiel
Nov 27 at 7:42
I was able to add all the printers configuration while building the docker image itself. and I'm able to ping the printers using lpstat command. The thing is if I give print, they're stuck at not-completed state forever. Any way to debug this??
– Tywin Lannister
Nov 27 at 12:07
I'm not too familiar with CUPS itself, so maybe this will help: wiki.debian.org/DissectingandDebuggingtheCUPSPrintingSystem
– Haxiel
Nov 27 at 12:36
The VM would have CUPS set up to allow printing. The Docker container probably doesn't have that. You'll either need to set up CUPS inside the Docker container, or permit the container to access the host's CUPS configuration. OCP uses a very restricted configuration for containers by default.
– Haxiel
Nov 27 at 7:42
The VM would have CUPS set up to allow printing. The Docker container probably doesn't have that. You'll either need to set up CUPS inside the Docker container, or permit the container to access the host's CUPS configuration. OCP uses a very restricted configuration for containers by default.
– Haxiel
Nov 27 at 7:42
I was able to add all the printers configuration while building the docker image itself. and I'm able to ping the printers using lpstat command. The thing is if I give print, they're stuck at not-completed state forever. Any way to debug this??
– Tywin Lannister
Nov 27 at 12:07
I was able to add all the printers configuration while building the docker image itself. and I'm able to ping the printers using lpstat command. The thing is if I give print, they're stuck at not-completed state forever. Any way to debug this??
– Tywin Lannister
Nov 27 at 12:07
I'm not too familiar with CUPS itself, so maybe this will help: wiki.debian.org/DissectingandDebuggingtheCUPSPrintingSystem
– Haxiel
Nov 27 at 12:36
I'm not too familiar with CUPS itself, so maybe this will help: wiki.debian.org/DissectingandDebuggingtheCUPSPrintingSystem
– Haxiel
Nov 27 at 12:36
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
The VM would have CUPS set up to allow printing. The Docker container probably doesn't have that. You'll either need to set up CUPS inside the Docker container, or permit the container to access the host's CUPS configuration. OCP uses a very restricted configuration for containers by default.
– Haxiel
Nov 27 at 7:42
I was able to add all the printers configuration while building the docker image itself. and I'm able to ping the printers using lpstat command. The thing is if I give print, they're stuck at not-completed state forever. Any way to debug this??
– Tywin Lannister
Nov 27 at 12:07
I'm not too familiar with CUPS itself, so maybe this will help: wiki.debian.org/DissectingandDebuggingtheCUPSPrintingSystem
– Haxiel
Nov 27 at 12:36