Igor Pavlov

Yes, Deflate is default. Deflate can be extracted by any zip program. LZMA was added to zip specification later, and some zip unpackers do not support LZMA.

However linux diagnostics may show the information from the host OS, not the container, so it's misleading and could be the source of the problem. Yes, 7-zip sees: RAM size: 70213 MB CPU hardware threads: 36 So by default it tries to use up to 36 cpu threads and up to 80% from RAM size (80% from reported 70213 MB). -mmt2 switch will help you, because 2 threads will use only 400 MB of RAM, if -mx=7 switch is used. But what about previous container in your tests? Why did it work before? Is it bad configuration...

However linux diagnostics may show the information from the host OS, not the container, so it's misleading and could be the source of the problem. Yes, 7-zip sees: RAM size: 70213 MB CPU hardware threads: 36 So by default it tries to use up to 36 cpu threads and up to 80% from RAM size (80% from reported 70213 MB). -mmt2 switch will help you, because 2 threads will use only 400 MB of RAM, if -mx=7 switch is used. But what about previous container in your tests? Why did work before? Is it bad configuration...

However linux diagnostics may show the information from the host OS, not the container, so it's misleading and could be the source of the problem. Yes, 7-zip sees: RAM size: 70213 MB CPU hardware threads: 36 So by default it tries to use up to 36 cpu threads and up to 80% from RAM size (80% from reported 70213 MB). But what about perevious container in your tests? Why did work before? Is it bad configuration of container? What changes do you have?

I want to find the reason of problem. So we need 7z b log in that container with failure. Note that different linux systems can have different versions of 7-zip. So we need to know exact version of 7-zip of failure case.

I want to find the reason of problem. So we need 7z b log in that container with failure.

Correction. 7-zip doesn't use whole memory, if it knows correct memory size. Run 7z b it can show memory size reported to 7-zip.

I shows Threads:15 instead of your 2 vCPUs. -mx=7 and 15 cpu threads can require about 4 GB of RAM So maybe it was the problem. You can reduce the number of working threads with -mmt2 or -mmt4switch.