debugSymbolsQuarkusContainer: Error: OCI runtime error: cannot set memory swappiness with cgroupv2

Karm / mandrel-integration-tests

Integration tests for GraalVM and its Mandrel distribution. Runs Quarkus, Helidon and Micronaut applications and small targeted reproducers. The focus is solely on native-image utility and compilation of Java applications into native executables.

Apache License 2.0

5 stars 3 forks source link

debugSymbolsQuarkusContainer: Error: OCI runtime error: cannot set memory swappiness with cgroupv2 #56

Closed Karm closed 2 years ago

Karm commented 3 years ago

Latest podman, maybe OS issues? TODO: try on latest Fedora

jerboaa commented 3 years ago

@Karm I'm intrigued. How would I reproduce this?

jerboaa commented 3 years ago

Is anything in this test setting --memory-swappiness? From the man page of podman run:

   --memory-swappiness=number
       Tune a container's memory swappiness behavior. Accepts an integer between 0 and 100.

       This flag is not supported on cgroups V2 systems.

Karm commented 3 years ago

@jerboaa It is caused by this line: https://github.com/Karm/mandrel-integration-tests/blob/master/testsuite/src/it/java/org/graalvm/tests/integration/utils/BuildAndRunCmds.java#L66

Test case:

launch Q app in a container
launch gdb in a container
carry out gdb session inside the container

Is it really necessary to have it set to 0 for the session to work? I don't recall. Will try presently....

jerboaa commented 3 years ago

OK, this won't work on a cgroups v2 system. So I suggest to figure out why you need this swappiness setting in the first place and find out what the alternatives are to achieve the same (or similar) result. Perhaps setting --memory=X and --memory-swap=X would help to disable swap.