Skip to content

runner.aws_batch: Bump minimum Docker image required for overlays on AWS Batch#423

Merged
tsibley merged 1 commit intomasterfrom
trs/aws-batch/overlays
Mar 21, 2025
Merged

runner.aws_batch: Bump minimum Docker image required for overlays on AWS Batch#423
tsibley merged 1 commit intomasterfrom
trs/aws-batch/overlays

Conversation

@tsibley
Copy link
Contributor

@tsibley tsibley commented Mar 21, 2025

There is now no caveat¹ of AWS Batch overlays being partial while Docker and Singularity overlays are complete. Overlays are complete and behave the same across containerized runtimes.

Spurred by conversation in review² and realizing, after some tinkering, that it would not take too much extra effort after all to implement in the image entrypoint.

¹ As mentioned in "runner.aws_batch: Support overlay volumes (e.g.
--augur)" (99168ac).

² #419 (comment)

Checklist

…AWS Batch

There is now no caveat¹ of AWS Batch overlays being partial while Docker
and Singularity overlays are complete.  Overlays are complete and behave
the same across containerized runtimes.

Spurred by conversation in review² and realizing, after some tinkering,
that it would not take too much extra effort after all to implement in
the image entrypoint.

¹ As mentioned in "runner.aws_batch: Support overlay volumes (e.g.
  --augur)" (99168ac).

² <#419 (comment)>
@tsibley tsibley merged commit c664274 into master Mar 21, 2025
45 checks passed
@tsibley tsibley deleted the trs/aws-batch/overlays branch March 21, 2025 19:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant