docker-build.tar does not include broken symlinks
See original GitHub issueDescription
Symlinks might not point to anything on the host system, but be useful inside the container.
More importantly this is different from the standard Docker behavior.
Info
-
d-m-p version : 0.27.2
-
Maven version (
mvn -v
) : 3.5.2 -
Docker version : 18.06.1-ce
-
Sample project : https://github.com/jakub-bochenski/demp-link-problem/tree/master/test
Check the sample output in https://github.com/jakub-bochenski/demp-link-problem/blob/master/README.md
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
COPY resolves symlinks it shouldn't try to resolve #1111
Actual behavior Since v0.18.0, COPY tries to resolve some symlinks it shouldn't try to resolve, which is a regression.
Read more >How to specify different .dockerignore files for different builds ...
Now I'm trying to use Docker to run my unit tests, and in this case I want the tests directory included. I've checked...
Read more >Docker for Windows 2.x release notes
Compose-on-Kubernetes is no longer included in the Docker Desktop installer. You can download it separately from the compose-on-kubernetes release page.
Read more >podman-build
podman build Builds an image using instructions from one or more Containerfiles or Dockerfiles and a specified build context directory. A Containerfile uses...
Read more >Docker Images : Part III - Going Farther To Reduce Image Size
We will talk about standardizing base images, stripping binaries, assets optimization, and other build systems or add-ons like DockerSlim or ...
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 Free
Top 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
Sorry for the late response, November is crazy busy with travelling for me. Actually I think this should be an option in the Maven archiver used for creating that tar, so that symlinks get resolved before being included into the tar. Need to check that, but I’m afraid can’ t do it before mid December. Please ping me again in case I should forget it.
PS. What I find really strange here is that apparently nobody ever hit this issue before.
Another thought: maybe it would be worth checking out how https://github.com/mojohaus/rpm-maven-plugin is handling this. (Specifically http://www.mojohaus.org/rpm-maven-plugin/map-params.html)