Add a default ignore pattern when dockerFileDir is root project dir
See original GitHub issueWhen the dockerFileDir
is the same as ${project.baseDir}
then it makes sense to have a default exclude for target/**
when building the docker image.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
How to include files outside of Docker's build context?
The best way to work around this is to specify the Dockerfile independently of the build context, using -f. For instance, this command...
Read more >Dockerfile reference - Docker Documentation
The CLI interprets the .dockerignore file as a newline-separated list of patterns similar to the file globs of Unix shells. For the purposes...
Read more >How to use .dockerignore and its importance - Shisho Cloud
Let's learn how to use .dockerignore for efficient Docker image ... Usually, you put the Dockerfile in the root directory of your project, ......
Read more >fabric8io/docker-maven-plugin
Default output directory to be used by this plugin. ... is also treated as a FileSet exclude pattern as used by the maven-assembly-plugin....
Read more >Ignoring Code - ESLint - Pluggable JavaScript Linter
Glob patterns in ignorePatterns are relative to the directory that the config file is ... by creating a .eslintignore file in your project's...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I also find this quite confusing. I have my Dockerfile in the project root, and I can easily build it with
docker build -t some/name .
But in order to make this work with docker-maven-plugin, I have to create a.maven-dockerinclude
file which IMHO is counter-intuitive. I would prefer that the plugin was more compatible with standard Docker.Sure --> https://github.com/fabric8io/docker-maven-plugin/tree/master/samples/smallest or https://github.com/fabric8io/docker-maven-plugin/tree/master/samples/zero-config