If you want to extract only .log files from an archive:
Incorrect (Shell tries to expand):
unzip logs.zip *.log
# Error if no .log files exist in current directory
Correct (Unzip handles the logic):
unzip logs.zip '*.log'
To extract everything inside stage/ (which might contain subfolders), use:
unzip archive.zip "stage/*"
The quotes prevent shell expansion. unzip receives the literal pattern stage/* and matches all entries under stage/.
sudo dtruss unzip archive.zip "stage/*" 2>&1 | grep -i "open"
This reveals exactly what filenames unzip is looking for inside the ZIP's central directory.
For a path like stage components/components2/file.txt, extract using:
unzip archive.zip stage\ components/\*
The backslash escapes the space for the shell, and * is passed to unzip.
If you continue to face issues, consider switching to python with zipfile module for programmatic extraction, where you have full control over matching logic:
import zipfile
with zipfile.ZipFile('archive.zip') as zf:
for member in zf.namelist():
if member.startswith('stage/components/'):
zf.extract(member)
This eliminates any ambiguity with wildcards entirely. If you want to extract only
Troubleshooting the "unzip cannot find any matches for wildcard specification" Error
If you are working with automated build pipelines, AWS CLI, or simple shell scripts, seeing the error unzip: cannot find any matches for wildcard specification "stage/components/*" can be frustrating.
This error typically happens because of how the shell (like Bash or Zsh) interacts with the unzip utility. The Root Cause: Shell Expansion
In most Linux and macOS environments, the shell tries to be helpful. When you type a wildcard like *, the shell tries to "expand" it before the unzip command even runs.
If the directory or file you are referencing doesn't exist in the current working directory exactly as typed, the shell fails to find a match and passes the literal string (including the asterisk) to unzip. unzip then looks for a file literally named * and fails. The Solution: Wrap it in Quotes
The quickest and most effective fix is to escape the wildcard so that the shell ignores it and passes it directly to the unzip utility. Option 1: Single or Double Quotes (Recommended)
By putting the path in quotes, you tell the shell: "Don't touch this; let the unzip program handle the wildcard."
unzip "stage/components/*" # OR unzip 'stage/components/*.zip' Use code with caution. Option 2: Backslash Escaping
You can also "escape" the wildcard character specifically using a backslash. unzip stage/components/\* Use code with caution. Common Scenarios Where This Occurs 1. AWS CLI and S3 Correct (Unzip handles the logic):
unzip logs
If you are downloading a zipped artifact from S3 and trying to unzip it into a specific folder structure within a CI/CD pipeline (like GitHub Actions or GitLab CI), the environment might not have the local folder tree mapped out yet. Always quote your paths in your .yml configurations. 2. Extracting Specific Subdirectories
If you only want to extract a folder named components located inside a stage directory within the zip file: unzip archive.zip "stage/components/*" -d ./destination Use code with caution. 3. Case Sensitivity
Remember that Linux file systems are case-sensitive. If your folder is actually named Stage/Components, the wildcard specification stage/components/* will fail even if you use quotes. Summary Checklist If you're still seeing the error, check these three things: Quotes: Is your wildcard path wrapped in ' ' or " "?
Path Accuracy: Does the internal structure of the .zip file actually match stage/components/? (Run unzip -l archive.zip to check the contents without extracting).
Permissions: Does the user running the command have read access to the source and write access to the destination?
By simply quoting the wildcard, you ensure that unzip receives the instructions correctly, bypassing the shell's interference.
This error typically occurs when the command is unable to find the files matching your wildcard pattern within a ZIP archive, or when the shell (like Bash or Zsh) incorrectly tries to expand those wildcards before the tool can see them. Ask Ubuntu It is frequently seen during Oracle installations
where the installer script tries to extract staging components (like stage/Components/* ) and fails due to quoting issues or corrupted downloads. Oracle Forums 1. Fix the Wildcard Syntax
The most common cause is that the shell is trying to match the wildcard against files in your current local directory instead of searching the ZIP file. Unix & Linux Stack Exchange Quote the pattern To extract everything inside stage/ (which might contain
: Wrap your wildcard specification in single or double quotes so it passes directly to unzip file.zip stage/Components/*.jar unzip file.zip 'stage/Components/*.jar' Escape the wildcard
: Alternatively, use a backslash before the asterisk to prevent shell expansion. unzip file.zip stage/Components/\*.jar Stack Overflow 2. Verify File Integrity (Corrupted Downloads)
If quoting doesn't work, the "cannot find" error often implies the zip file is truncated or the directory structure is missing. Oracle 10g Installation Error :JRE missing in scratch path
The error message "unzip: cannot find any matches for wildcard specification" typically occurs when a user tries to extract specific files using wildcards (like *) and the shell expands that wildcard before the unzip command can process it. In many cases involving complex software installers like Oracle, this error is a sign that the installation media is incomplete or the current working directory is incorrect. 1. The Root Cause: Shell vs. Internal Expansion
The primary technical reason for this error is a conflict between how your terminal (shell) and the unzip utility handle special characters.
Shell Expansion: By default, shells like Bash try to match wildcards against files already present on your disk before running the command. If no files on your disk match the pattern, the shell passes the literal string to unzip, which may then fail if it doesn't see the expected archive.
Missing Files: Specifically for the "stage components" error (common in Oracle 10g/11g installers), it often means a required directory—such as ../stage/Components/oracle.swd.jre/—is physically missing from the extracted files. 2. Immediate Fixes and Workarounds
Depending on whether you are running a manual command or an automated installer, use the following solutions: For Manual Commands (CLI)
If you are typing a command like unzip *.zip, the shell may expand this into multiple arguments, which unzip does not support.
JRE missing in scratch path" or "Error writing to directory" errors