# A more scalable, container-friendly self-hosted runner: Container Agent - now in Open Preview

**URL:** <https://discuss.circleci.com/t/a-more-scalable-container-friendly-self-hosted-runner-container-agent-now-in-open-preview/45094>\
**Category:** Build Environment\
**Created:** [August 16, 2022, 8:20pm UTC](https://discuss.circleci.com/t/a-more-scalable-container-friendly-self-hosted-runner-container-agent-now-in-open-preview/45094 "2022-08-16T20:20:41Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![Almenon](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/almenon/32/32566_2.png) [@Almenon](https://discuss.circleci.com/u/Almenon)\
**Post date:** [April 17, 2023, 10:33pm UTC](https://discuss.circleci.com/t/a-more-scalable-container-friendly-self-hosted-runner-container-agent-now-in-open-preview/45094/21 "2023-04-17T22:33:45Z")

</div>

Thanks for making the container runner! I just set it up in EKS. I’m wondering whether artifacts, workspaces, or caches work with the container runner?

---

<div class="post-metadata">

**Author:** ![sebastian-lerner](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/sebastian-lerner/32/27833_2.png) [@sebastian-lerner](https://discuss.circleci.com/u/sebastian-lerner)\
**Post date:** [April 18, 2023, 12:34pm UTC](https://discuss.circleci.com/t/a-more-scalable-container-friendly-self-hosted-runner-container-agent-now-in-open-preview/45094/22 "2023-04-18T12:34:39Z")

</div>

They do all work: [CircleCI’s self-hosted runner FAQs - CircleCI](https://circleci.com/docs/runner-faqs/#how-do-caching-workspaces-and-artifacts-work-with-circleci-self-hosted-runners)

---

<div class="post-metadata">

**Author:** ![Almenon](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/almenon/32/32566_2.png) [@Almenon](https://discuss.circleci.com/u/Almenon)\
**Post date:** [May 4, 2023, 3:34pm UTC](https://discuss.circleci.com/t/a-more-scalable-container-friendly-self-hosted-runner-container-agent-now-in-open-preview/45094/23 "2023-05-04T15:34:29Z")

</div>

That’s great! I’m assuming we pay network transfer to internet costs and CircleCI manages the storage and retention of the caches on your side?

I imagine if we want to avoid network and CircleCI storage costs we could build out our own orb that saves to a S3 bucket with a lifecycle policy 🤔

---

<div class="post-metadata">

**Author:** ![sebastian-lerner](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/sebastian-lerner/32/27833_2.png) [@sebastian-lerner](https://discuss.circleci.com/u/sebastian-lerner)\
**Post date:** [May 4, 2023, 4:34pm UTC](https://discuss.circleci.com/t/a-more-scalable-container-friendly-self-hosted-runner-container-agent-now-in-open-preview/45094/24 "2023-05-04T16:34:13Z")

</div>

We do manage the storage and retention on our side. You pay for the network transfer from CircleCI’s storage to your self-hosted runner as “Network Egress”. and the Storage is also charged [Persisting Data Overview - CircleCI](https://circleci.com/docs/persist-data/#managing-network-and-storage-usage)

You are free to use your own storage/network mechanisms. It just won’t be as trivial as the built-in functionality.

[Previous page](https://discuss.circleci.com/t/a-more-scalable-container-friendly-self-hosted-runner-container-agent-now-in-open-preview/45094.md?page=1)