Make CI use both Apptainer and Docker with ROCm 7.0 #154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR updates the CI workflow to support both Apptainer and Docker container runtimes, automatically detecting and using whichever is available on the system. Both containers now use ROCm 7.0 as their base image, ensuring consistency across different container environments.
Changes
Docker Container Updates
rocm/vllm-dev:nightly_aiter_integration_final_20250325torocm/pytorch:rocm7.0_ubuntu22.04_py3.10_pytorch_release_2.8.0to match the Apptainer definitionApptainer Container Updates
CI Workflow Updates
build-docker-image) and Apptainer (build-apptainer-image) that run conditionally based on detectioncontents: read) to all workflow jobs for security best practicesContainer Detection Priority
Benefits
Testing
Resolves the issue by enabling CI to use whichever container environment is available on the system while ensuring both use ROCm 7.0.
Original prompt
Fixes #153
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.