Separate Folder for Podman

[alokdutt-pangaea]

Primary meant for WSL but can be used on a linux VM as well.

WIndows 11 -> WSL (OracleLinux_8_10) -> Podman (rootless) -> containers
DB connection port is exposed to windows for siebel tools

Containerization/Podman/oraclelinux/classic-mde/manage/scripts/automate-architecture/launch-siebel -

1. Modified scripts for podman
2. additional scripts for kafka and sidecar

Containerization/Podman/oraclelinux/classic-mde/manage/scripts/automate-architecture/generic/container

1. Modified scripts for podman

Containerization/Podman/oraclelinux/classic-mde/manage/scripts/automate-architecture/db

1. instructions for DB parameters and plugging DB
2. Modified scripts for podman

Please give it a try. Suggestions and improvements are welcome.

[alokdutt-pangaea]

@blacksheep-crm please review this draft PR when you get a chance.. Thanks !

[OracleSiebel]

Hi Alok,

Many thanks for the pull-request. I'm not currently in a position to spend time testing this. Given that you've put everything into a completely separate folder, I'm inclined to let it pass quickly. Before I do, I'd just like to understand why you felt the need for a separate podman folder? We moved to podman long ago, admittedly with an older version of the system presented here, but were able to succeed with almost no change. The basic requirement was to install the podman-docker package to provide the alias. I think there were some other minor changes. Given you have an entirely separate folder here, I can't easily review and understand the changes. Can you give a little more detail please?

Regards,

Duncan

[alokdutt-pangaea]

Hi Duncan,

Thanks for reviewing!
The setup is running on Windows 11 via WSL2 (Oracle Linux 8.10). I'm using rootless Podman, and while most Docker and Podman commands are similar, there are a few differences in how rootless Podman behaves:

1. I created a separate folder to avoid modifying the original Docker scripts. Only specific scripts were changed — not all.
2. Since I'm using rootless Podman, I had to rely on Netavark for container name resolution.
3. Health checks had to be handled manually; otherwise, containers remained stuck in the "starting" state. This seems to be a rootless Podman quirk and is addressed in the launch script.
4. For dropDB19 even with some modifications, it only extracted the files. Additional steps were needed to plug in the DB and configure parameters.
5. some extras like kafka and sidecar containers in launch-siebel.

Thanks,
Alok