The Wayback Machine - https://web.archive.org/web/20200920201814/https://github.com/GoogleContainerTools/jib/issues/2275
Skip to content

/ jib

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

Jump to bottom

Jib should maintain hard-links and symlinks #2275

Open
briandealwis opened this issue Feb 10, 2020 · 2 comments
Open

Jib should maintain hard-links and symlinks #2275

briandealwis opened this issue Feb 10, 2020 · 2 comments
Labels
P3 good first issue help wanted

Comments

@briandealwis
Copy link
Member

@briandealwis briandealwis commented Feb 10, 2020

The hardlinking supported by the Spotify docker-client can result in large image-size savings for situations using lots of hard-links (jvanzyl/dockerfile-maven#2). Jib should track hard-links. Jib should also preserve symlinks (perhaps only if they reference within the layer?).
@jvanzyl
Copy link

@jvanzyl jvanzyl commented Feb 10, 2020

Great savings in the time to produce the image as well, give far less material is transferred.
@briandealwis briandealwis added the P3 label Feb 10, 2020
@briandealwis
Copy link
Member Author

@briandealwis briandealwis commented May 28, 2020

The relevant starting point is com.google.cloud.tools.jib.api.buildplan.FileEntriesLayer#addEntryRecursive().
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 good first issue help wanted
3 participants
@jvanzyl @briandealwis @chanseokoh
You can’t perform that action at this time.