The Hidden Truth About File Deletion: Docker, MinIO, and Storage Layers Explained

●3
calendar_today ago • schedule1 min read
— Originally published at medium.com

I assumed for a long time that delete meant gone. Like, actually gone — bytes wiped, storage reclaimed, done.

It doesn’t work that way. And once I understood what actually happens at the storage layer, a bunch of confusing behavior I’d run into with Docker volumes and MinIO suddenly made sense.

A file isn’t one thing
Take report.pdf. It looks like a single object on your disk. It's not.

🔥 Join developers growing publicly
Share your knowledge, build in public, and grow your developer presence with a global community.

More Posts

My 30-day log cleanup kept a file that was 30 and a half days old

BashSnippets - Oct 8

I escaped the dot correctly and sed still rewrote a file marked DO NOT CHANGE

BashSnippets - Oct 13

What Developers Already Know About Data Center Delays

Tom Smithverified - Sep 28

AAIF Hits 10 Projects. Its CTO on What to Adopt Now and the Security Gaps Left Open

Tom Smithverified - Oct 23

A Textile Mill's Dyehouse Ramp Curve: Get One Step Wrong and the Sheet Belongs to the Master

aiomniu - Oct 18
chevron_left
124 Points • 3 Badges
Birmingham, England • t.co/MKGUwfqrab
1Posts
0Comments

Related Jobs

Commenters (This Week)

4 comments
4 comments
2 comments

Contribute meaningful comments to climb the leaderboard and earn badges!