• The main component of an IPFS node is Kubo (formerly go-ipfs)
• there is a Web UI that connects to kubo's "admin" API
• the Desktop app packages both into an electron app to easily install locally
• kubo can also run on a server (like cloudron - which I'm working on)
• the Web UI can access it via freshly added Auth
• you can also install a local node AND one on cloudron - and peer them
  • "pinning" data on the cloudron node to have it available from e.g. your laptop if your desktop is offline
  • your local node acts as a local-first "cache", and if you have accessed the data you need once, you're fully local-first without needing the cloudron node
  • (or if the cloudron node is offline, but the data is stored on any other server on the IPFS network)

ipfs has a Docker image and a tutorial on how to run IPFS in Docker:

https://docs.ipfs.io/how-to/run-ipfs-inside-docker/

Are you referring to running the desktop app on a remote server running Cloudron or getting the desktop app from a IPFS node running on Cloudron to install locally?
If the desktop app is installed on a remote Cloudron how would it be runned from an actual desktop, which interface, a viewer, a browser?

https://docs.ipfs.io/how-to/run-ipfs-inside-docker/

Although I'm kinda hoping that some of my content disappears for good !

IPFS is a far more robust means of archiving content like a webpage than a site like archive.is. A lot of people are justifiably concerned about information (and huge amounts of work) being lost due to censorship or websites closing. IPFS is better capable of distributing archives so there is less danger of them being lost.

Unless I am missing something about this app request, Cloudron cannot really run desktop apps.

One strong reason to use Cloudron to run ipfs-desktop (a desktop app) is security and privacy.

If you are using IPFS to pin (seed/publish) content, the IP address of your node is broadcasted (so that other IPFS nodes can find and retrieve content your node is making available.)

Running ipfs-desktop inside a container is good for security. Using a VPN is useful too, so as to disassociate your node from your own IP address. Putting ipfs-desktop inside a simple Virtual Machine might be one possibility.

https://github.com/ipfs/go-ipfs
https://js.ipfs.io/

The thing is, people might want to start pinning content on IPFS, but not want to rely on a big pinning company to do so.

There is an excellent talk introducing the concepts here by Steve Allen:

https://invidious.snopyta.org/watch?v=0IGzEYixJHk

The best way to get started with ipfs, I think, is to try ipfs-desktop.

Check out Awesome IPFS to see a gallery of IPFS tools:
https://awesome.ipfs.io/tools/

Galacteek is a little appreciated IPFS tool which has tons of functionality (blog, webpage, messaging) when you are familiar with things:
https://galacteek.gitlab.io/download/#pimp-my-dweb