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

Vessel creates different layers for files that haven't been changed #11

Open
alan-ghelardi opened this issue May 31, 2020 · 0 comments
Open
Assignees

Comments

@alan-ghelardi
Copy link
Collaborator

alan-ghelardi commented May 31, 2020

Expected Behavior

Subsequent builds run over unchanged files must produce layers with the same SHA256.

Actual Behavior

Vessel produces layers with different SHA256 hashes for files that haven't been changed at all.

Steps to Reproduce the Problem (if it's a bug)

  1. Run vessel containerize on a given project and save the resulting tarball as v1.tar.
  2. Run vessel containerize on the same project without modifying anything and save the resulting tarball as v2.tar.
  3. Inspect the archives and notice that the layers created by Vessel have different hashes for each execution.

Additional Info

  • Vessel version: 0.2.128.
  • Clojure version: any
  • Java version: any

This issue is critical because prevents Vessel from leveraging layers, exactly the purpose that motivated its creation. I need to investigate further, but I guess that the issue has been introduced after this pull request: #4.

@alan-ghelardi alan-ghelardi self-assigned this May 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant