Technology

59415 readers

2886 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

463

It looks a lot like VMware just lost a 24,000-VM customer • The Register (www.theregister.com)

submitted 5 months ago by [email protected] to c/[email protected]

75 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 11 points 5 months ago* (last edited 5 months ago)

Similar to docker, but the technical differences matter a lot. VMs have a lot of capabilities containers don't have, while missing some of the value on being lightweight.

However, a more direct (if longer) answer would be: all cloud providers ultimately offer you VMs. You can run docker on those VMs, but you have to start with a VM. Selfhosted stuff (my homelab, for example) will also generally end up as a mix of VMs and docker containers. So no matter what project you're working on at scale, you've probably got some VMs around.

Whether you then use containers inside them is a more nuanced and subtle question.