Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Bunny magic containers

I understand that they now offer persistent volumes. Anybody using them to host n8n or any of the regular selfhosted stuff? What's the experience been like?

Comments

  • Do they still require you to push your Docker image to a third party service to deploy?

  • I tried running beszel on it. It worked fine! Only issue was setting up smtp relay! They block the use of even external relay by default. But a ticket to support team and got it working.

  • LeviLevi Member

    Is it glorified vps or is it requires docker?

  • @Levi said:
    Is it glorified vps or is it requires docker?

    Docker images only.

    Thanked by 1Levi
  • @network said:
    Do they still require you to push your Docker image to a third party service to deploy?

    So basically you need another VPS to use their sub-VPS?

  • @DataRecovery said:

    @network said:
    Do they still require you to push your Docker image to a third party service to deploy?

    So basically you need another VPS to use their sub-VPS?

    Worse, they only seem to have 2 options, push your image to either GitHub or DockerHub (or deploy a public image from either of them). Both of them charge a lot more than a LowEndVPS to store private images.

    Thanked by 1DataRecovery
  • rpqurpqu Member

    @network said:

    @DataRecovery said:

    @network said:
    Do they still require you to push your Docker image to a third party service to deploy?

    So basically you need another VPS to use their sub-VPS?

    Worse, they only seem to have 2 options, push your image to either GitHub or DockerHub (or deploy a public image from either of them). Both of them charge a lot more than a LowEndVPS to store private images.

    Huh? Push it using github action

  • @rpqu said:

    @network said:

    @DataRecovery said:

    @network said:
    Do they still require you to push your Docker image to a third party service to deploy?

    So basically you need another VPS to use their sub-VPS?

    Worse, they only seem to have 2 options, push your image to either GitHub or DockerHub (or deploy a public image from either of them). Both of them charge a lot more than a LowEndVPS to store private images.

    Huh? Push it using github action

    Storing private images in GitHub Container Registry costs money after the first 500MB. I guess you could push, deploy, and immediately delete the image every time.

  • I'd never heard of deano, why do they insist on that

  • rpqurpqu Member

    @network said:

    @rpqu said:

    @network said:

    @DataRecovery said:

    @network said:
    Do they still require you to push your Docker image to a third party service to deploy?

    So basically you need another VPS to use their sub-VPS?

    Worse, they only seem to have 2 options, push your image to either GitHub or DockerHub (or deploy a public image from either of them). Both of them charge a lot more than a LowEndVPS to store private images.

    Huh? Push it using github action

    Storing private images in GitHub Container Registry costs money after the first 500MB. I guess you could push, deploy, and immediately delete the image every time.

    https://docs.github.com/en/billing/concepts/product-billing/github-packages

    Billing for container image storage: Container image storage and bandwidth for the Container registry is currently free.If you use Container registry, you'll be informed at least one month in advance of any change to this policy. For more information about the Container registry, see Working with the Container registry.

  • @rpqu said:

    @network said:

    @rpqu said:

    @network said:

    @DataRecovery said:

    @network said:
    Do they still require you to push your Docker image to a third party service to deploy?

    So basically you need another VPS to use their sub-VPS?

    Worse, they only seem to have 2 options, push your image to either GitHub or DockerHub (or deploy a public image from either of them). Both of them charge a lot more than a LowEndVPS to store private images.

    Huh? Push it using github action

    Storing private images in GitHub Container Registry costs money after the first 500MB. I guess you could push, deploy, and immediately delete the image every time.

    https://docs.github.com/en/billing/concepts/product-billing/github-packages

    Billing for container image storage: Container image storage and bandwidth for the Container registry is currently free.If you use Container registry, you'll be informed at least one month in advance of any change to this policy. For more information about the Container registry, see Working with the Container registry.

    Thanks, not sure how I missed that!

Sign In or Register to comment.