podman save results in jenkins error java.io.IOException: Insufficient disk space to extract resource. 0 available, 9 required.

[tushae01]

I am setting up Jenkins on an Alma 9 instance. I'm new to podman. I have the docker alias set up. The jenkins pipelines still use the docker maven plugin and the rapid7 jenkins plugin. I'm able to build and deploy, but there is an error on the step where rapid7 tries to save the image.
The image is 306 MB
From the command prompt within the workspace, I can run docker save or podman save without error.
From the command prompt at jenkins home, podman save or docker save returns this message - Error: docker-archive doesn't support modifying existing images
From the jenkins job log (x's for masking) -
[r7sdlc.tmpxxxx] $ docker image ls --no-trunc xxxx.dkr.ecr.xxx.amazonaws.com/xxxx
Creating image bundle...
[r7sdlc.tmpxxxx] $ docker save sha256:xxxx -o image.tar
Analyzing image xxx.dkr.ecr.xxx.amazonaws.com/xxxx...
Extracting image data...
Analyzing image data...
Encountered an exception.
java.io.IOException: Insufficient disk space to extract resource. 0 available, 9 required.
at com.rapid7.container.analyzer.docker.service.DockerImageAnalyzerService.untar(DockerImageAnalyzerService.java:287)
at com.rapid7.container.analyzer.docker.service.DockerImageAnalyzerService.analyze(DockerImageAnalyzerService.java:134)
at com.rapid7.sdlc.plugin.jenkins.ContainerAssessmentBuilder$AnalyzeCallable.call(ContainerAssessmentBuilder.java:544)
at com.rapid7.sdlc.plugin.jenkins.ContainerAssessmentBuilder$AnalyzeCallable.call(ContainerAssessmentBuilder.java:518)
at hudson.remoting.LocalChannel.call(LocalChannel.java:47)
at com.rapid7.sdlc.plugin.jenkins.ContainerAssessmentBuilder.perform(ContainerAssessmentBuilder.java:263)
at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:101)
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:71)
at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:840)
Continuing anyway because 'fail on plugin failure' is disabled...

From the jenkins log -
Jan 29 18:16:21 xxxx jenkins[xxxxx]: 2024-01-29 18:16:21.431+0000 [id=1648]#011INFO#011c.r.c.a.d.s.DockerImageAnalyzerService#analyze: Extracting image to /xxxx/workspace/xxxx/r7sdlc.tmpxxxx/extract/imagexxxx.
Jan 29 18:16:21 xxxx systemd[xxxxx]: podman-60664.scope: Consumed 3.157s CPU time.
Jan 29 18:16:21 xxxx jenkins[xxxxx]: 2024-01-29 18:16:21.836+0000 [id=1648]#011WARNING#011c.r.c.a.d.s.DockerImageAnalyzerService#untar: [Image: image.tar] File failed to extract /xxxx/workspace/xxxxx/r7sdlc.tmpxxxx/extract/imagexxxx/xxxx/layer.tar.

df -h (tried this larger instance to see if it would help to no avail )
Filesystem Size Used Avail Use% Mounted on
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 16G 168K 16G 1% /dev/shm
tmpfs 6.3G 8.6M 6.3G 1% /run
/dev/nvme0n1p2 150G 5.2G 145G 4% /
/dev/nvme1n1 200G 7.2G 193G 4% /srv
tmpfs 3.2G 28K 3.2G 1% /run/user/986
tmpfs 3.2G 4.0K 3.2G 1% /run/user/4455

I've attached podman info and the /etc/containers/storage.conf(renamed to storage.txt)
storage.txt
podman_info.txt
rapid7 plugin info - https://github.com/jenkinsci/rapid7-insightvm-container-assessment-plugin/blob/master/src/main/java/com/rapid7/sdlc/plugin/jenkins/ContainerAssessmentBuilder.java

Could you point me in the right direction?
Thanks!