-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make singleton container readonly #937
Conversation
019bbf4
to
51949e5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did we consider using the AWS CLI image plus some awk
as a replacement for jq
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We talked about this, but I think it represents an extra level of scope creep on a ticket that's already crept up massively, and could probably be a separate investigation.
7462c69
to
b0dd129
Compare
Co-authored-by: Natasha <[email protected]>
b0dd129
to
df4860f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
What does this change?
Create a custom docker image for the singleton container, so we don't need to install awscli and jq.
Why?
This is part of the work to resolve AWS FSBP ECS.5 (No write access to root file system by default
How has it been verified?
Tested on CODE to verify expected behaviour for one job, and multiple concurrent ones.
What next
Create a reusable workflow for creating container images, as we now have 3 of these. This will be done in a follow-up PR