Replies: 3 comments 1 reply
-
Wildcard patterns are evaluated by a shell. When you run a command on your host system When you run the command in a container, using You need to ensure:
Try something like...
|
Beta Was this translation helpful? Give feedback.
-
This works. However, it adds an increased level of complexity. I've created this container for a class I'm teaching and trying to keep things as simple as possible for the students, who will be a mixture of undergraduates with no coding experience and graduate students with varying levels of coding experience. Adding the /bin/sh -c and quoting the command will introduce a new level of explanation that's needed. It's already a struggle with students to get them to simply use Do you think it would be easier to bind the directory and then use the container as |
Beta Was this translation helpful? Give feedback.
-
Indeed, that does seem to solve the problem.
I'll experiment with this and see if I can get it to work for the students. Thank you for the help. This inspired a potential solution. |
Beta Was this translation helpful? Give feedback.
-
I have created a container and want to analyze multiple files from the host system. I've bound the directory using --bind and can access single files but wildcards are not working to access all of them.
Is it possible to use wildcards when working with a mounted host directory?
If so, how?
I have tried:
It works as expected.
However, there are three files in the directory and I want to analyze them all. Normally, when not using a container, the following will work. For example:
But in this case, it does not.
The eventual goal is to use this on many more files than just three. Calling each individually is not a viable option.
Beta Was this translation helpful? Give feedback.
All reactions