-
Notifications
You must be signed in to change notification settings - Fork 109
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
v1.2.1 appears to have introduced a destination path bug #249
Comments
Weird, I just got this error on 1.2.0 |
Oh well - there goes the idea it was related to the 1.2.1 changes :-( Regardless, @goldmann if you find time to investigate I'm more than happy to add some debug code or other changes into my local docker squash to help analyse this (given I have a consistently reproducible case). Thanks again for the product. |
Hm, do you have maybe an image that could be used as a reproducer? And invocation. |
Same issue with 1.2.1 in our CI 1.2.0 :
1.2.1 :
|
@ypapouin Are you able to provide a reproducer ? |
No I'm not able to, but looking on code changes 0030222, It looks like
|
Sorry @goldmann - didn't see this come through. Unfortunately I can't provide a reproducer either but I'm happy to run tests, add debug, etc.. (although appreciate it's not the the easiest (or desirable) path to debug an issue).. |
What am I supposed to offer you? A Image or an environment or something? |
os: my cmd : docker-squash -f 2 -t aaaaa:v1 test:v1.0 image: run docker instpect ,and get layers "RootFS": { run docker history test:v1.0 get |
my image will multiple commit containers saved as new image, This is the only thing that could possibly be different from normal image |
Got the same issue as well...The last layers got added as docker commits and trying to sqash them all together is resulting in the same output. Squashing all layers work. Looks like the issue comes up, when there are layers to move. The layers in my case are mostly ''. For me the output before the crash looks like this:
|
Only tested that with 1.2.1, but I can try 1.2.0 as well. |
@RyDoRe Can you provide the command line you were using please? |
docker-squash -v -f 4 -t image:squashed-tag image:that_I_squashed Was quite straight forward. I have 42 layers in total. It crashes with trying to squash only the upper4 layers and succeeds with all layers |
The way I reproduced this with a test image: |
I just released 1.2.2. |
When our CI build squashes with v1.2.0 all works fine. When we update to v1.2.1, docker-squash consistently produces the following error:
For now I've fixed our CI build on 1.2.0 but obviously would prefer to be on the latest and greatest :-) Any suggestions of things to try (or a v1.2.2 release 😁) most appreciated..
Thanks in advance,
Steve.
The text was updated successfully, but these errors were encountered: