[BUG] Kantra failing on fedora + podman

[jmle]

Is there an existing issue for this?

• I have searched the existing issues

Konveyor version

0.5.3

Priority

Critical

Current Behavior

When running a normal analyze command:

kantra analyze --input /home/jmle/Dev/redhat/40SampleApps/spring-app-4 --target cloud-readiness --output ~/Dev/redhat/40SampleApps/spring-app-4.report --overwrite --log-level 500 --rules ~/Dev/redhat/go/src/rulesets/default/generated/spring

I am getting the following error repeated five or six times:

Error: lsetxattr /home/jmle/.local/share/containers/storage/volumes/edeznyKmLagztoDv/_data/.classpath: operation not permitted
ERRO[0000] container run error                           error="exit status 126"
INFO[0000] starting first provider                       provider=java
/usr/bin/podman run -d --rm --name abylQxKjdOmKvIFS --network yjmWuxozabDkxIwE -v edeznyKmLagztoDv:/opt/input/source:z quay.io/konveyor/java-external-provider:v0.5.3 --port=37429DEBU[0000] executing command                             args="run -d --rm --name abylQxKjdOmKvIFS --network yjmWuxozabDkxIwE -v edeznyKmLagztoDv:/opt/input/source:z quay.io/konveyor/java-external-provider:v0.5.3 --port=37429" cmd= container tool=/usr/bin/podman
time="2024-09-27T17:14:15+02:00" level=warning msg="Using cgroups-v1 which is deprecated in favor of cgroups-v2 with Podman v5 and will be removed in a future version. Set environment variable `PODMAN_IGNORE_CGROUPSV1_WARNING` to hide this warning."

and then it exits without having analyzed the application.

Expected Behavior

Kantra should analyze the application without errors

How Reproducible

Always (Default)

Steps To Reproduce

1. Run the above analysis or similar on a sample application
2. See the errors

Environment

• Fedora Linux 40
• Podman 5.2.2
• Kantra 0.5.3

Anything else?

No response

[konveyor-ci-bot]

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

[jmle]

It seems to be a problem with my local environment... closing for now