Live data from Hacker News

Defence Against the Docker Arts

blog.heroku.com

81–90 of 103 posts

Re: Defence Against the Docker Arts

#82

Earlier quoted context omitted.

At the end of the day a docker image (or qemu, firecracker, etc...) is just a tarballed root filesystem. The funny thing to me is how seemingly overly complex the ecosystem has become for turning a blueprint for a Linux system into a tarball of files and folders. What am I missing?

Layers?

But aren't they just an implementation detail, albeit a useful one? You'd find copy-on-write deltas in modern snapshotting filesystems too.

Re: Defence Against the Docker Arts

#83
It took me a while to get the pun, it doesn't show up in the article anywhere from what I could fine and I don't actually see how you're defending against anything here so I wonder - Did you just have this pun sitting around and were itching to use it somewhere, anywhere?

Re: Defence Against the Docker Arts

#85

It took me a while to get the pun, it doesn't show up in the article anywhere from what I could fine and I don't actually see how you're defending against anything here so I wonder - Did you just have this pun sitting around and were itching to use it somewhere, anywhere?

Personally, I still don't get it; would you please care to explain? I'm really confused with what does the title really try to convey... :/

edit: Also, clicking to the article, the actual title seems (now?) to be: "Turn Your Code into Docker Images with Cloud Native Buildpacks", so I'm even more confused now... o_O

Re: Defence Against the Docker Arts

#86
post #10

Here’s a little known fact: “docker build” can trivially be extended to build buildpacks or CNB. Now that the buildkit refactoring is complete, Dockerfiles are just the default frontend. There’s already a buildpack frontend in the community repo, and it works great. Writing your own frontend is real straightforward. Honestly after years of stagnation, the most exciting work on container building is now coming out of…

At the end of the day a docker image (or qemu, firecracker, etc...) is just a tarballed root filesystem. The funny thing to me is how seemingly overly complex the ecosystem has become for turning a blueprint for a Linux system into a tarball of files and folders. What am I missing?

The benefit is versioning the OS configuration alongside the application for more reliability.

I think the main problem is trying to apply the same patterns to stateful and stateless services.

Re: Defence Against the Docker Arts

#87
post #85

It took me a while to get the pun, it doesn't show up in the article anywhere from what I could fine and I don't actually see how you're defending against anything here so I wonder - Did you just have this pun sitting around and were itching to use it somewhere, anywhere?

Personally, I still don't get it; would you please care to explain? I'm really confused with what does the title really try to convey... :/ edit: Also, clicking to the article, the actual title seems (now?) to be: "Turn Your Code into Docker Images with Cloud Native Buildpacks" , so I'm even more confused now... o_O

it's a reference to she who cannot stop tweeting

Re: Defence Against the Docker Arts

#88

Vote me down, but oh god that title...

I mean, I'm pretty much through with talking to people about docker. There are so many morons out there trumpeting the buzzword, and they are just total imbeciles. My last pointy-haired boss thought he could manipulate the conversation to discover what I know about containerizing EC2 instances, by guiding the conversation with leading questions that'd get me to spill my guts with nerd signaling and posturing, so that…

Seek help or some tea with a valium, you seem like you're in need of both.

Re: Defence Against the Docker Arts

#90

Earlier quoted context omitted.

Layers?

But aren't they just an implementation detail, albeit a useful one? You'd find copy-on-write deltas in modern snapshotting filesystems too.

Parent was comparing against a tarball, not a snapshotting filesystem.
Post reply on HN