# Switches for resource constrained VPS?

**URL:** https://meta.discourse.org/t/switches-for-resource-constrained-vps/383216
**Category:** Self-hosting
**Created:** [September 19, 2025, 1:07am UTC](https://meta.discourse.org/t/switches-for-resource-constrained-vps/383216 "2025-09-19T01:07:54Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![nineb](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nineb/32/522106_2.png) [@nineb](https://meta.discourse.org/u/nineb)
#### Post date: [September 29, 2025, 9:23am UTC](https://meta.discourse.org/t/switches-for-resource-constrained-vps/383216/4 "2025-09-29T09:23:30Z")

</div>

> [@pfaffman](#):
>
> You could try creating the swap, building the container, shutting down the container, and removing the swap.

I tried the next best thing with two SSH windows. create swap, run launcher, other ssh window delete swap, launcher continued. And this might work on a better provisioned VPS. On my next spare I will try it. I have an instance now running on 4c12r

> [@itsbhanusharma](#):
>
> You should contact your cloud provider to provision a larger disk for you.

Given: cannot increase resources

Suggestion: increase resources

---

_[View the full topic](https://meta.discourse.org/t/switches-for-resource-constrained-vps/383216)._