Hello! I am having an issue executing this command docker run alpine cat /etc/*release* on my macOS 10.13.1. I get a response of zsh: no matches found: /etc/*release* When I use online playgrounds like katacoda to try the command, it works fine. What could be wrong on my side please?

any help please? I have done so much googling to no success.

When you run that command, zsh tries to expand /etc/*release* itself instead of passing it to the command to be executed in docker. So it actually tries to look up /etc/*release* in your local MacOS installation and fails to find it, leading to that error message. What you should actually do is run…

Thank you Johan. This explains it, however, alpine uses ash for its bash so the updated command that worked is docker run alpine /bin/ash -c “cat /etc/*release*”

No, it doesn’t :wink: % docker run -it --rm alpine / # ls -l /bin/sh /bin/ash lrwxrwxrwx 1 root root 12 Jan 16 21:52 /bin/ash -> /bin/busybox lrwxrwxrwx 1 root root 12 Jan 16 21:52 /bin/sh -> /bin/busybox Glad I could be of help.

[image] johanmulder: /bin/sh -c I actually arrived here after googling the issue. Thanks. I’m trying to make sense of this command by checking the documentation. It’s not the easiest to make sense of. Any chance you can explain what the command is actually doing? Thanks either way!

[image] abdulwahabadi: Any chance you can explain what the command is actually doing? I’m not sure if it will answer your question but let me share something with you: from the below, I can conclude that even if the cat command is executed in a contained the local presence of the same filena…

[image] adrianbaran690: if the cat command is executed in a contained the local presence of the same filename and path is required. It probably is a MacOS-only issue. It is not just a macOS issue. You replied to an old question so I don’t think @abdulwahabadi is still waiting for the answer, …

So it actually tries to look up /etc/release in your local MacOS installation and fails to find it, leading to that error message. No. Wrong. You can put the * in quotes and it won’t interpret it locally. eg docker exec ff2 ls "/etc/*" ls: /etc/*: No such file or directory The container actua…

I’m not wrong. Read and interpret my answer again: [image] johanmulder: When you run that command, zsh tries to expand /etc/*release* itself instead of passing it to the command to be executed in docker

I know this is a revived dead thread, but do you know why is it that cat fails to find matching files when not specifying the /bin/sh -c part in your command?

Error executing command with docker run

Docker Desktop

rimelek (Ákos Takács) October 16, 2024, 2:43pm 13

It has nothing to do with cat. It is shell expansion. Without running a shell with the command as argument between quotation marks you use the host shell and the command will be sent to the container only after the shell on the host interpreted it. And you need to define a shell, because just using quotation marks makes the defined command to be a reference to a single executable. Which will not exist.

Topic		Replies	Views
Executable file not found in $PATH (Alpine Linux) General docker	4	16179	August 13, 2023
Enable docker commands run without sudo Docker Desktop macos	14	26467	April 23, 2023
Executing a binary file in docker which is in the PATH General docker	0	3375	February 22, 2016
Run docker command within container General docker , beta	2	1946	August 17, 2016
Shell pipeline and docker run -i Docker Desktop	2	1793	May 1, 2016

Error executing command with docker run

Related topics