Live data from Hacker News

Gocker: Docker implemented in 1.3k lines of Go

unixism.net

71–80 of 89 posts

Re: Gocker: Docker implemented in 1.3k lines of Go

#71
post #46

My 2018 joke has been implemented. > Or Gocker, an implementation of Docker in go... https://news.ycombinator.com/item?id=16119842

As a kid I was a compulsive liar and would make up non-existent stories.

With the advent of search engines I discovered that any story I can come up with actually happened somewhere in the world and has an article about it already.

Re: Gocker: Docker implemented in 1.3k lines of Go

#72
post #26
post #25

Can someone explain the value/purpose of docker to someone who (easily) deploys regular apps to a Digital Ocean droplet?

Reproducibility is the biggest value in my opinion. A Dockerfile encapsulates all the messy dependencies in a single isolated environment. This also makes deployments easier too.

Check out https://buildpacks.io for a better approach (in my opinion) in terms of maintainability, patching, updating.

Keeping a Dockerfile uptodate can be hell, especially if you have many apps that need to be patched... Updating base image is not sufficient, gotta update all downstream dockerfiles as well :-/

Re: Gocker: Docker implemented in 1.3k lines of Go

#73
post #49
post #24

Earlier quoted context omitted.

While I tend to agree, I think LoC can give a sense of scale for large systems and at least a tiny bit of insight about its potential complexity. I recently worked with a client on an integration effort that had to touch many different points on a (massive, for me) codebase with tens of millions of LoC. For that, LoC was the only reasonable metric I could come up with to try and convey the scale and complexity of the…

I assume you probably can't share the client, but can you share the general domain of the software?

General domain is modeling and simulation

Re: Gocker: Docker implemented in 1.3k lines of Go

#74
post #56
post #46

My 2018 joke has been implemented. > Or Gocker, an implementation of Docker in go... https://news.ycombinator.com/item?id=16119842

Lol. Should link the root though, plenty of suggestions for others: https://news.ycombinator.com/item?id=16117172

And no one thought of Focker written in F#?

Re: Gocker: Docker implemented in 1.3k lines of Go

#75
post #71
post #46

My 2018 joke has been implemented. > Or Gocker, an implementation of Docker in go... https://news.ycombinator.com/item?id=16119842

As a kid I was a compulsive liar and would make up non-existent stories. With the advent of search engines I discovered that any story I can come up with actually happened somewhere in the world and has an article about it already.

Hence, everyone is wrong and right at the same time, citation needed of course.

Re: Gocker: Docker implemented in 1.3k lines of Go

#76

Pretty cool, and very educational for people not familiar with how these things work That said (and I've said this before), this is not really Docker. It's running containers, not the same thing. If you want to compare it to anything, it's runc, but that's not a good headline :) Not that the docker architecture is that clean, but it is the combination of ideas it brought to the table what made docker docker: - have A…

> If you want to compare it to anything, it's runc, but that's not a good headline :)

I don’t know, gunc is a pretty good name.

Re: Gocker: Docker implemented in 1.3k lines of Go

#78
post #74
post #56

Earlier quoted context omitted.

Lol. Should link the root though, plenty of suggestions for others: https://news.ycombinator.com/item?id=16117172

And no one thought of Focker written in F#?

Is It too soon to talk about the C implementation?

Re: Gocker: Docker implemented in 1.3k lines of Go

#79
post #25

Can someone explain the value/purpose of docker to someone who (easily) deploys regular apps to a Digital Ocean droplet?

The joke that I think actually explains it pretty well is that it eliminates the "well it works on _my_ machine" problem, by not just shipping the code, but shipping the machine.

*shipping the userland

It's not the equivalent of handing over a VM image. You're still open to unintended sensitivity to kernel versions, for instance.

Post reply on HN