That’s a good point, Lars! I’ll try to update the post shortly to accomodate this, and will take it into consideration when doing the concrete evaluations.

There’s no very large risk of data leakage, not always, but, specially with programs that work over proprietary data formats or local databases there’s a risk of access loss.

When the USA imposed sanctions on my country, at the start many companies closed access immediately.

This included companies like Adobe, and the people here who subscribed to Adobe programs instead of pirating them lost access to using the software they paid to use.

Once many companies realized the embargo was against political actors, many reopened, and I’m so happy to be able to give Adobe my money again…

Yet others never reopened. If for some reason I decided I wanted to keep using VirtualBox, I’d need to use a VPN to download it.

Thanks for leaving your thoughts. Unfortunately, I fear you’re right that things will get worse before they get better. On the upside (for those of us outside of the US), the focus on these problems is becoming stronger all the time, and new services and resources into alternatives are going up.

Hi andrewc, thanks for reaching out.

It’s a bit hard to say why this happens without knowing more about your setup, but essentially, it sounds like your containers’ data storage is not being mapped to persistent storage but stored in memory or on some non-persistent volume.

Most containers that you download from Docker Hub, etc., will have some description of which internal path they recommend mapping to persistent storage like Docker volumes or Bind mounts.

I’m not sure I can be more helpful without knowing more, such as the type of container and the parameters used to deploy it.