←back to thread

128 points darthShadow | 3 comments | | HN request time: 0.001s | source
Show context
ricardbejarano ◴[] No.42812378[source]
Run your own registry.
replies(3): >>42812402 #>>42812415 #>>42812602 #
TZubiri ◴[] No.42812415[source]
Or run no registry. Here's a port from a Dockerfile to just a vm:

FROM Debian

CMD apt-get install thing

CMD curl blabla/install.sh

Pretty much converts to:

aws-cli ec2 launch-instance

ssh user@server apt-get install thing

ssh user@server curl blabla/install.sh

In general, everytime you dispense of a high level abstraction, the solution is not to replicate the high level abstraction, but to build directly at a lower level abstraction.

If you want to replace burgers, just buy a slab of meat and put it in the fire or bake your own bread. You don't need to make preservants and buy artificial sweeteners, etc...

replies(7): >>42812470 #>>42812473 #>>42812476 #>>42812525 #>>42812526 #>>42812553 #>>42812606 #
the-grump ◴[] No.42812553{3}[source]
Yeah, no.

I'm not only using containers to deploy my VPSes.

Thank you for trying.

P.S. at least use something declarative and provider-agnostic like terraform.

replies(1): >>42812782 #
1. TZubiri ◴[] No.42812782{4}[source]
What else are you using containers for?
replies(1): >>42814883 #
2. yjftsjthsd-h ◴[] No.42814883[source]
Testing things on my laptop and deploying services to my home lab. Both benefit enormously from the minimal overhead, fast deployment, and ease of completely removing a service once I'm done with it.
replies(1): >>42817362 #
3. TZubiri ◴[] No.42817362[source]
Ah yes, that was one of the main selling points of docker early on, fixing the "works on my machine".

The way I solve that problem is by working directly on testing/staging servers which have the same specs as production.

I almost never run stuff on my local machine, and if I do it's a well isolated piece of code whose IO signature I know exactly and I can mock external systems with ease.