返回资讯中心
外部精选
软件工程
#开发者实时流

Probably the least productive container you'll ever run

This is probably the least productive container you'll ever run.

Hacker News 最新bdeshi2026/10/18 · 2026/10/184 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

This is probably the least productive container you'll ever run.

It's for those times when your Docker Compose stack or Kubernetes deployment needs a container that doesn't actually need to do anything.

It does absolutely nothing, just to keep your container orchestrator happy. It even waits for SIGINT or SIGTERM before leaving, because apparently, doing nothing isn't enough; it has to do nothing responsibly.

podman run --rm -d ahmubashshir/unemployd:latest

Replace podman with docker if that's your thing.

See example.yaml for Kubernetes or Compose.

podman build -t unemployd .

Or use Docker. Whatever keeps you employed.

Q: Why does this exist?

A: The orchestrator wanted a container. Who am I to argue?

Q: What does it do?

A: Absolutely nothing. Please don't distract it.

Q: Only Docker Hub?

A: Nope! GHCR1 too.

Q: Should I use it?

A: If you need a container that does nothing, you've come to the right place.

Q: Why not just use sleep infinity?

A: You dare want a proper rootfs just to sleep on it?

Q: Does it consume resources?

A: It consumes a PID, some memory, and less than one AF2 sector.

Q: Why is it called unemployd?

A: It got the job. It just doesn't do the job.

Q: Does it support graceful shutdown?

A: Of course. Even unemployed daemons have to know when to leave.

Q: Is this production-ready?

A: It's production-nothing.

Q: Why did you create it?

A: I had nothing better to do.

License

See LICENSE.

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →