Your System Details

• Badfish Version: sha256:0791aec303bc9732274ba52462103fb29ce1cf17907210772b14f15622a3ecbc
• Python Version: 3.9.7 (within container)
• Operating System: Official Podman Container (Alpine Linux)
• Target System Type: Dell R6615
• IPMI / Out-of-band Firmware Version: iDRAC 9

Describe the Bug
Running multiple Badfish commands over time causes iDRAC to hit the session limit. Sessions are not properly closed, leading to a lockout.

To Reproduce

1. Run Badfish commands repeatedly (e.g., --check-virtual-media, --mount-virtual-media, etc.)

2. After several runs, Badfish/iDRAC fails to authenticate.

3. iDRAC reports:

   RAC0218: The maximum number of user sessions is reached...
   

4. The only workaround is to wait ~20 minutes or perform a physical power drain (unplug + hold power button for 20 seconds).

Expected Behavior
Badfish should clean up sessions automatically, or offer a flag to close them explicitly after execution.

Logs / Screenshots

RAC0218: The maximum number of user sessions is reached. Make sure that the number of active sessions is less than or equal to 
the threshold limit. To end a current session and start a new session, do one of the following:
  1. Log out of iDRAC by using a Graphical User Interface (GUI).
  2. End any unused session by running the following RACADM command at the Command Line Interface (CLI): racadm closessn -i 
     [session id]. Warning: Ending a session may abruptly stop any running operation on that specific iDRAC session.

Additional Details
This occurs even when no long-running operations are performed. Sessions accumulate silently until iDRAC refuses further logins. No way to recover via Redfish or GUI once the limit is hit — only a full physical power drain resolves the issue.

Also, would you consider publishing versioned Podman image tags to improve reproducibility? I'm currently relying on the SHA256 digest as a workaround.