DevOps Community Sponsored by Cloud Posse

SweetOps

out of curiosity, are most folks here running ARC with docker-less runners? i'm quite interested in pushing for daemonless github actions jobs, but im trying to think of how significant the lift would be. in theory, switching to something like podman as a drop in replacement for docker actions should _work?_

We used ARC for many years and Summerwind before that 

But it’s so much easier just to deploy runs-on.com

That’s what we exommend these days and you dont need to deal with Docker in docker, get virtually unlimited scale, faster caching with magic cache that uses s3 and is fully self host 

<https://github.com/cloudposse-terraform-components/aws-runs-on|https://github.com/cloudposse-terraform-components/aws-runs-on>

<@U05G0A3NBSQ> while I understand the appeal as ops, developers are probably going to be angry that they have to fiddle with many edge cases compared to what works on github-hosted runners. Getting ARC right can be a huge time sink, for comparably lower performance in the end compared to bare VMs (disclaimer: I'm the author of RunsOn). And thanks <@UB2EH889X> for the shoutout!

ive been looking at runs-on (we even started using the public cache action) and it does seem appealing, but not sure if the team is ready for a move off ARC

does runs-on support the express one zone s3 feature that was released? im not sure how it’d work in runs-on architecture, but in k8s land, I think that’d be potentially super speedy using s3 mount point or something

<@U05G0A3NBSQ> since the S3 express one zone specifically requires choosing a single AZ, you would have to use RunsOn with an `external` networking stack that only has one AZ, and then configure the bucket + add the permission as a custom policy to the RunsOn stack. So it's possible, but I would recommend starting with standard S3 across multiple AZs (helps with reliability and finding the cheapest instance types), and see if the S3 backend is really the bottleneck (most probably not, it will be the network speed).

If you mainly need fast read access to data files, setting up an <https://github.com/awslabs/mountpoint-s3|s3 mountpoint> on the default S3 bucket is also possible, as well as using <https://runs-on.com/caching/efs/|EFS> since the latest version.