Feature Request: Support for Docker in Addition to Podman
Currently, racs is hard-coded to use podman for all image builds, as noted in the limitations section of the README. However, many users and developers may prefer to work with Docker due to its widespread usage and compatibility.
Proposed Solution:
It would be beneficial to introduce a configuration option that allows users to choose between podman and docker for building images. This could involve:
- Adding a configuration flag that specifies the desired container engine.
- Abstracting the image build steps to accommodate differences between podman and docker commands, if any.
Benefits:
- Increases the flexibility of
racs and makes it more appealing to a broader audience.
- Allows users already invested in Docker to easily integrate
racs into their existing workflows without needing to switch container engines.
Implementing this feature would enhance the usability of racs and align it with common practices in the community.
Feature Request: Support for Docker in Addition to Podman
Currently,
racsis hard-coded to usepodmanfor all image builds, as noted in the limitations section of the README. However, many users and developers may prefer to work with Docker due to its widespread usage and compatibility.Proposed Solution:
It would be beneficial to introduce a configuration option that allows users to choose between
podmananddockerfor building images. This could involve:Benefits:
racsand makes it more appealing to a broader audience.racsinto their existing workflows without needing to switch container engines.Implementing this feature would enhance the usability of
racsand align it with common practices in the community.