-
Notifications
You must be signed in to change notification settings - Fork 787
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Glob COPY is failing #3318
Comments
Worked for me with 1.21.1
|
In case anyone comes across this, there was a |
¡THANKS! 👏🏼 👏🏼 I think that the error/exception is very poor of information. They must says some similar to "no items matching glob in |
We support .containerignore (Preferred, as well as overriding the path). |
Would this error message have helped?
|
How about: |
Yes! For me, any mention to .containerignore/.dockerignore in the message is really good. |
Users have accidently had a .containerignore or .dockerignore file in their context directly which blocked all content. Currently we report that no globs matched, but do not identify where the globs came from. This change is an attempt to add this data to the error. Example: containers#3318 Signed-off-by: Daniel J Walsh <[email protected]>
Users have accidently had a .containerignore or .dockerignore file in their context directly which blocked all content. Currently we report that no globs matched, but do not identify where the globs came from. This change is an attempt to add this data to the error. Example: containers#3318 Signed-off-by: Daniel J Walsh <[email protected]>
Users have accidently had a .containerignore or .dockerignore file in their context directly which blocked all content. Currently we report that no globs matched, but do not identify where the globs came from. This change is an attempt to add this data to the error. Example: containers#3318 Signed-off-by: Daniel J Walsh <[email protected]>
Users have accidently had a .containerignore or .dockerignore file in their context directly which blocked all content. Currently we report that no globs matched, but do not identify where the globs came from. This change is an attempt to add this data to the error. Example: containers#3318 Signed-off-by: Daniel J Walsh <[email protected]>
Users have accidently had a .containerignore or .dockerignore file in their context directly which blocked all content. Currently we report that no globs matched, but do not identify where the globs came from. This change is an attempt to add this data to the error. Example: containers#3318 Signed-off-by: Daniel J Walsh <[email protected]>
Users have accidently had a .containerignore or .dockerignore file in their context directly which blocked all content. Currently we report that no globs matched, but do not identify where the globs came from. This change is an attempt to add this data to the error. Example: containers#3318 Signed-off-by: Daniel J Walsh <[email protected]>
Users have accidently had a .containerignore or .dockerignore file in their context directly which blocked all content. Currently we report that no globs matched, but do not identify where the globs came from. This change is an attempt to add this data to the error. Example: containers#3318 Signed-off-by: Daniel J Walsh <[email protected]>
Users have accidently had a .containerignore or .dockerignore file in their context directly which blocked all content. Currently we report that no globs matched, but do not identify where the globs came from. This change is an attempt to add this data to the error. Example: containers#3318 Signed-off-by: Daniel J Walsh <[email protected]>
Users have accidently had a .containerignore or .dockerignore file in their context directly which blocked all content. Currently we report that no globs matched, but do not identify where the globs came from. This change is an attempt to add this data to the error. Example: containers#3318 Signed-off-by: Daniel J Walsh <[email protected]>
Description
Glob COPY is failing on very basic case
Steps to reproduce the issue:
Describe the results you received:
all files matching the glob are filtered
Describe the results you expected:
all files matching the glob should be copied without error
Output of
rpm -q buildah
orapt list buildah
:Output of
buildah version
:Output of
podman version
if reporting apodman build
issue:Output of
cat /etc/*release
:Output of
uname -a
:Output of
cat /etc/containers/storage.conf
:The text was updated successfully, but these errors were encountered: