Dominik

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....

Only tested that with 1.2.1, but I can try 1.2.0 as well. The Image I'm having issues with I unfortunately can't provide. but I can take a look, if i...

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...

The way I reproduced this with a test image: I used e.g. the mariadb:latest image, ran a container of that and created e.g. a folder, commited those changes to the...

The container runs in a k3s cluster with debian11/12

Unfortunately I'm not able to provide you with that, as this crash only happens with the large dataset we have in production and I'm not allowed and able to forward...

I'm going to talk with my team about it and will inform you on how we want to proceed. Thank you for looking into it!

For the sake of completeness, here is the explicit Dockerfile and startup-script: Dockerfile: ``` FROM manticoresearch/manticore:6.3.0 ENV TZ=Europe/Berlin RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone RUN apt-get...

I think we were able to narrow down the issue quite a bit... The issues we are having is related to the number of sources we are trying to use...

The sources dataschema are identical. We use joins with the sql_joined_field in some of the indexes querys, but not to tables that are used in other indexes or that depend...