I won't say you cannot or shouldn't backup a container since it it wrong imo, but as your using docker as a base i'd say just backup mapped volumes and configuration files. Docker is built around breaking and rebuilding your container and keep working anyways as long as your mapped volumes and docker configurations are the same (asuming you use a well maintained image for updates or something of your own).
That's probably the sane way to do it and will save you space. I don't see the benefit of a full container backup (unless it's an lxc, lxd container or another full persistent container type).
As for the backup repository you can use whatever. If it were me i'd use another server or a NAS, but most cloud storage provider would fit. Storage is never free though.
Self hosting is en mostly about keeping control of your data, paying capex instead of opex and having something to play/learn with. If you don't need any of those you probably don't wanna self host tbf.
Lots of people here have quite a large media collection and storage costs can addup pretty quick in opex. I basically have 15TB of media in Jellyfin so just imagine the cost of that in public cloud.