Skip to content
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

Is ** in dockerignore meant to match files as well? #21807

Open
1 task done
cowwoc opened this issue Jan 14, 2025 · 0 comments
Open
1 task done

Is ** in dockerignore meant to match files as well? #21807

cowwoc opened this issue Jan 14, 2025 · 0 comments
Labels
status/triage Needs triage

Comments

@cowwoc
Copy link

cowwoc commented Jan 14, 2025

Is this a docs issue?

  • My issue is about the documentation content or website

Type of issue

Information is incorrect

Description

Per https://docs.docker.com/build/concepts/context/#matching:

Docker also supports a special wildcard string ** that matches any number of directories (including zero)

but looking at https://github.com/moby/patternmatcher/blob/main/patternmatcher.go#L322 the implication seems to be that foo/** will match any file or directory that is a child of directory foo. Meaning, ** will match paths that end with a file, not just a directory.

Is my interpretation correct?

Location

https://docs.docker.com/build/concepts/context/#matching

Suggestion

No response

@cowwoc cowwoc added the status/triage Needs triage label Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/triage Needs triage
Projects
None yet
Development

No branches or pull requests

1 participant