Transfer of docker to Infomaniak Hosting

[MyQ]

Chatgpt notes on mirgration/upgrade
Post by MyQ » Thu Nov 27, 2025 1:43 pm

Below is a clear, safe, step-by-step guide explaining what is and isn’t possible when trying to transfer a Docker project from a Raspberry Pi 5 (ARM64, Debian) to Infomaniak shared hosting.

First: The Important Reality

Infomaniak shared hosting does not support Docker, containers, or any root-level Linux features.
So you cannot “transfer a Docker container” and run it there.
Shared hosting ≠ VPS ≠ Cloud.
If you want to run Docker on Infomaniak, only their VPS or Cloud servers support it.
What You Can Do
Depending on your goal, here are the valid migration paths:

Option A — “Deploy the same project without Docker (shared hosting compatible)”
This works if your RPi 5 Docker container is hosting something like:

a PHP app
a static site (HTML/JS/CSS)
a Node.js app (not supported on cheap shared hosting)
a Python app (not supported on shared hosting)
✔ Shared hosting supports:
PHP (8.x)
MySQL/MariaDB
Static files
Cron jobs
Basic terminal (no root)

Shared hosting does not support:

Node.js apps
Python web servers
Docker
Custom daemons
Background services
How to migrate if it's a PHP/static project:
Extract your app from Docker
On your Raspberry Pi:
docker cp <container_name>:/var/www/html ./site
Or wherever your app files live.
Recreate config (not the container!)
Move .env variables to Infomaniak’s environment manager
Export databases separately using mysqldump
Upload the files
Via SFTP
Or Infomaniak file manager
Import your database via Infomaniak’s phpMyAdmin.
If you tell me what your container runs, I can generate an exact migration script.

Option B — "Move Docker exactly as-is" → Requires Infomaniak VPS
If you need to run the container unchanged, you need:
Infomaniak VPS (minimum 2–4 GB RAM if ARM → AMD64 re-build is needed).

Steps:
Save image on the Raspberry Pi
docker save -o myapp-arm64.tar myapp

Transfer the file
Example using SCP:
scp myapp-arm64.tar user@your-vps.ip:/home/user/

Load it on the VPS
docker load -i myapp-arm64.tar
Important:
Raspberry Pi = ARM64
Infomaniak VPS = AMD64
So the container may not run unless:
You rebuild using multi-arch:
docker buildx build --platform linux/amd64 -t myapp:amd64 .

Or your app is architecture-agnostic (e.g., Node + JS only)
If you want, I can generate a full multi-arch Dockerfile for you.

Option C — “Convert to Infomaniak Web App Hosting / Managed Hosting”

Infomaniak also offers:
Managed WordPress
Managed Node/VPS
Static hosting
If your RPi container runs a common framework, I can map it to the correct Infomaniak service.
⚠ To give you the exact migration steps
I need to know what your Docker container actually runs:
Please tell me:
What’s inside your container?
PHP?
Node.js?
Python?
A database?
A reverse proxy?
Do you want to keep using Docker, or is a simple hosting OK?
Shared hosting or VPS at Infomaniak?
If you reply with those 3 answers, I can generate:
a complete migration plan
specific commands
exact Dockerfile rebuilds
or a ZIP of files ready to deploy
Just let me know what type of project your RPi container contains.

-------------------------------------------------------------------------------------------

Transfer of docker to Infomaniak Hosting
Post by MyQ » Thu Nov 27, 2025 1:36 pm

Docker CANNOT be installed on actual oravox.com we must migrate either to a VPS, or cloud in order to install docker in Infomaniak. It is possible to install docker developed software on actual hosting using a compatible PHP version, but this requires much manual intervention and ongoing administration.
Please note actual PHP of oravox.con is actually 8.1, but is near end of life and will need to upgraded very soon.
If we use the VPS hosting, this cannot be automatically transferred later to the cloud hosting.
Please give me feedback as to which hosting option would be best, i feel that upgrading to cloud directly would be better because this can be dynamically sized, instantly. I we see too much traffic to the site the VPS cannot be quickly modified to handle more users.
I am unfamiliar with Docker Development only server side install and debug, so I cannot accurately calculate the impact to the programmers.
I invite all to comment in this forum your thoughts on this choice, or advice so we can move forward with the project in the best way for all.

[google]
Docker ne peut pas être installé sur le site oravox.com. Nous devons migrer vers un VPS ou le cloud pour l'installer sur Infomaniak. Il est possible d'installer un logiciel développé avec Docker sur un hébergement existant en utilisant une version PHP compatible, mais cela nécessite une intervention manuelle importante et une administration continue.
Veuillez noter que la version de PHP utilisée par oravox.con est actuellement la 8.1, mais elle arrive en fin de vie et devra être mise à jour très prochainement.
Si nous utilisons un hébergement VPS, la migration vers le cloud ne sera pas automatique. Merci de me faire part de vos suggestions quant à l'option d'hébergement la plus adaptée. Je pense qu'une migration directe vers le cloud serait préférable, car elle permet une adaptation dynamique et instantanée des ressources. En cas de forte augmentation du trafic sur le site, le VPS ne pourra pas être rapidement dimensionné pour gérer un plus grand nombre d'utilisateurs.
Je ne suis pas familier avec le développement Docker, seulement avec l'installation et le débogage côté serveur. Je ne peux donc pas évaluer précisément l'impact sur les développeurs.

Je vous invite à partager vos réflexions et vos conseils sur ce choix afin que nous puissions avancer au mieux dans ce projet.

[Marcel]

I had a look at their offers and for me the right choice for us at the moment is the VPS.
Their basic offer gives us enough resources to host multiple services. The only downside is
when the machine is down we can't access any of our services.
To me we can go with the VPS for now and move to their cloud offer if needed.
The key here is to isolate our services with docker to facilitate their management.

NB: We will be responsible of backing up our data ourselves.

[MyQ]

I understand your position, I have reservations on VPS because of upgrade possibilities which are slow, and limited.

The base Cloud VPS, has 4 cpu 12G ram 250G disk would this be enough to start? This way we can dynamically allocate resources as and when needed instantly totally avoiding user overload or other stuff that can crash the server

[Marcel]

That should be plenty.
Let's we have these 4 services on our VPS:
1. PHPBB ( + db)
2. The main oravox website (+ db)
3. Dev environment for the player
4. Dev environment for the website

We can configure docker to allocate minimal amount of resources to PHPBB, and the dev environments and give all available resources to the website since it's where most of our user interactions occur. Plus we won't have millions of user overnight (I wish we do, someday).
Now my question is: Is it possible to have access to the Object Storage system with a VPS?

[MyQ]

last question, we have the choice of linux on the cloud VPS, we could use debian the same as the CubePi, or we could use ubuntu. do you or marcel have any preference they are almost the same.

[SergeV]

Ola friends....

Question : Peut on transférer le PHPBB et base de données sur un autre nom de domaine, comme providence.be pour alléger ?

------------------------------------

Question is: Is it possible to have access to the Object Storage system with a VPS?

RESPONSE gpt : - Oui, c’est tout à fait possible d’accéder à un système d’Object Storage depuis un VPS — et c’est même l’un des usages les plus courants.
Voici ce qu’il faut comprendre :

VPS + Object Storage : est-ce compatible ?

Oui, à 100 %.
Un VPS peut se connecter à n’importe quel Object Storage (S3, OpenStack Swift, Google Cloud Storage, Backblaze, etc.) via :
une API (S3 API le plus souvent),
un SDK (Python, Node.js, PHP…),
un outil en ligne de commande (s3cmd, rclone, aws cli, etc.).
Le VPS sert simplement de machine, donc tant qu’il peut établir une connexion Internet, il peut accéder à ton Object Storage.
Pourquoi combiner VPS et Object Storage ?
Parce que les deux se complètent parfaitement :

Le VPS
héberge ton application, ton studio Oravox, ta base de données, ton backend, etc.
effectue la logique : traitement, IA, API, calcul, streaming…


L’Object Storage
stocke les gros fichiers :
audio Oravox,
images,
vidéos,
JSON,
backups,
archives, etc.
à très bas coût, avec une disponibilité proche de 100 %

Exemple concret pour toi (Oravox)
Ton VPS pourrait :

générer un fichier audio,
le stocker automatiquement dans un Object Storage S3 (OVH, Scaleway, Wasabi…),
te renvoyer une URL sécurisée → que ton application Oravox utilise.
C’est exactement le modèle utilisé par les grandes plateformes.

Comment s’y connecter depuis un VPS ?
Les méthodes les plus courantes :
rclone → pour monter ton Object Storage comme un disque
aws-cli → compatible S3 (même pour OVH ou Scaleway)
s3cmd → simple pour scripts
SDK (Node, Python, Go…) → si tu développes une app
Exemple en Python :
import boto3
s3 = boto3.client(
"s3",
endpoint_url="https://s3.fr-par.scw.cloud", # exemple Scaleway
aws_access_key_id="clé",
aws_secret_access_key="secret"
)
s3.upload_file("audio.mp3", "mon-bucket", "audio.mp3")

Conclusion
Oui, un VPS peut accéder à un Object Storage sans aucune limitation.
Il suffit d’utiliser les identifiants API et l’URL du service.

Si tu veux, je peux t’expliquer :
quel Object Storage choisir selon ton budget,
comment le connecter à ton futur backend Oravox,
ou te faire un tutoriel pas à pas pour un fournisseur (OVH, Scaleway…).

[Marcel]

last question, we have the choice of linux on the cloud VPS, we could use debian the same as the CubePi, or we could use ubuntu. do you or marcel have any preference they are almost the same.

hello MyQ, I would go with debian.