how to keep shell environment included with slim

Expected Behavior

keep shell env after slim build

Actual Behavior

we run with shell include as:
docker-slim --report /root/slim.report.json build
--http-probe=false
--continue-after=1
--include-shell=true
--include-oslibs-net=true
--include-ssh-client=true
ndsmodeler:20240914
the contiainer seems still missing the shell environment.
[root@localhost ~]# docker exec -it caf51e6fff9d /bin/bash
OCI runtime exec failed: exec failed: unable to start container process: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown
[root@localhost ~]# docker exec -it caf51e6fff9d /bin/sh
OCI runtime exec failed: exec failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory: unknown
[root@localhost ~]# docker exec -it caf51e6fff9d sh
OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown
how can we keep the shell environment and basic os commands? the base image is CentOS Stream 8

Specifications

• Version: 1.40.11
• Platform: centos stream 8

Start by reproducing the docker-slim 1.40.11 build command with --include-shell=true on the CentOS Stream 8 image, then inspect the resulting container with /bin/bash, /bin/sh, and sh. Done means the documented shell environment and requested basic OS commands remain available after slimming.