Summary

This PR introduces significant enhancements to the Podman/Kubedock integration within the UBI9 base image, focusing on improved compatibility, usability, and automation for containerized workflows that rely on Podman, especially in environments where Kubedock is enabled.

Key Changes

1. Podman Wrapper System Overhaul

• New Wrapper Scripts:

  • podman-compose-down-wrapper.sh:
    Provides a robust replacement for podman compose down (or docker compose down) to ensure proper cleanup of containers/services, especially when running with Kubedock where standard compose down cannot directly shut down pods.

  • podman-interactive-wrapper.sh:
    Transparently intercepts problematic podman run -it ... invocations and replaces them with a workaround using podman exec, ensuring interactive sessions work reliably with Kubedock.
    The wrapper forcibly replaces any --user or -u options with the current user's numeric UID (via id -u), ensuring the container always runs as the invoking OpenShift user id, regardless of what is passed on the command line.

  • docker.sh:
    Emulates the Docker CLI using Podman, with logic to route commands through the appropriate wrapper when Kubedock is enabled.

• Enhanced podman-wrapper.sh:

  • Detects and delegates compose down and interactive run commands to the new specialized wrappers.
  • Ensures seamless user experience and compatibility with both standard Podman and Kubedock-enabled environments.

2. Dockerfile Updates

• Registers all new wrapper scripts in the image and sets up the environment variables for the Podman wrapper system.
• Ensures the Docker CLI emulation is available at /usr/bin/docker and all wrappers are properly installed and owned.

3. Kubedock Setup Improvements

• kubedock_setup.sh now:
  • Implements a retry loop to ensure kubeconfig permissions are set correctly
  • Dynamically constructs KUBEDOCK_PARAMS based on available environment variables (REQUEST_CPU, REQUEST_MEMORY, REAPER_KEEPMAX), allowing for more flexible resource and lifecycle management.

Testing

• Manual and automated tests performed for:
  • Interactive container sessions (podman run -it ...)
  • Compose up/down workflows
  • Kubedock-enabled and standard Podman environments
  • Permission handling for kubeconfig

Backward Compatibility

• All changes are additive and maintain compatibility with existing workflows.
• The wrappers only activate when Kubedock is enabled or when specific command patterns are detected.