[21pt] Change Docker builds of dockerfile to docker compose

[RobHanna-NOAA]

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

We currently use a Dockerfile and run "docker build" to create our docker images. A new option exists using a tool called "Docker Compose". As we move further into AWS tools, we will likely be forced to use docker compose.

First step: Research if podman can work with docker build or if it must use docker compose. Answering this question will figure out the urgency of this fix. Ultimately we want to do this anyways but it is likely to be a very large task.

We are also currently changing from Docker to Podman which will likely demand or prefer docker compose. Either way, we should make this leap.

[mluck]

podman build will create an image directly from an existing Dockerfile without modification. I was able to podman build the current Dockerfile.dev.

[RobHanna-NOAA]

Perfect. Then we can defer this one for now.

[mluck]

I did encounter an error when trying to run the container. I think this has to do with trying to set the Group ID in a rootless container, so some changes may be needed (e.g., in src/entrypoint.sh).

❯ podman run --rm -it -v ~/projects/dev/inundation-mapping/:/foss_fim -v /efs-drives/fim-dev-efs/fim-data/:/data -v ~/outputs/:/outputs -v ~/outputs/outputs_temp/:/fim_temp --name podman fim_4:dev-4.5.13.1-podman
Group ID: 1370800235 | Group Name: fim
setgroups: Invalid argument
setgid: Invalid argument
❯

[RobHanna-NOAA]

ya.. that is ok. that is part of a different card to figure out how to get podman to replace docker for us. Permissions are going to be the hardest part and we now have a "dockerfile.prod" that is a partial solution. Podman can't work with root users but we can figure that out