reyokh agreed, this issue with Docker represents a primary challenge we've faced, because docker does not allow resizing the container.
The workaround involves ensuring all plans offer the same disk space limit for Docker, but vary in the provided storage space. This method effectively mimics the desired outcome of plan upgrades.
For instance, consider two plans:
- Plan A: Allocates 10GB for Docker's disk space and an additional 10GB for the user's home directory storage.
- Plan B: Keeps the Docker disk space constant at 10GB (as Docker's limitations prevent alterations) and expands the user's storage to 50GB specifically for website content.
Upgrading from Plan A to B will successfully expand the user's available space.
As mentioned, Docker's restrictions are the root of this complication. We're exploring alternatives to bypass these limitations for more flexible future solutions. However, this represents our optimal approach under the current constraints.
