[21 pt (more)] Move from Docker to Podman

[RobHanna-NOAA]

Note: Now part of 1377 EPIC: FIM Sys Admin Tasks (and a few related FIM tasks)

This story is already WIP and is now considered urgent by ITSG. They are wanting to de-commission our two OWP servers and replace them with new servers. The new ones are based in RHEL8 which has podman and does not support docker.

One of the biggest requirements of Podman is that it can not use root users which all of our Docker images rely on, especially for AWS and external non Noaa users. One of the main requirements is the permissions part which is well underway and is covered in card [1335](Figure out the permissions for non-root users). There are complications in that task but it is moving forward.

Key notes:

• Podman is FOSS like Docker.
• Podman can use Docker build and run scripts but, while unconfirmed, looks like it prefers docker compose scripts and not docker build scripts. There is a seperate card for that fix which really should be done anyways regardless of this task.
• AWS can use Podman but it isn't simple and their native system is docker. This may create challenges.
• While maybe not the best option, we can consider using podman for OWP servers and Docker for external users and AWS.

This task was requests by ITSG on Oct 10th as they are WIP in trying to switch to the new OWP replacement server for our dev server.. They are getting very concerned about delays. In the last few weeks, we now have notice they want to upgrade our OWP prod server(s) as well.

A very large amount of research and testing is required here. Rob has a lot of notes and has already talked to various other folks on how to do this. We are focusing on finishing fixing the basic permissions issue first from Issue 1335 as it is a pre-req.