Run your own registry.
replies(3):
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...
Is this trolling? Who gives a shit? It's 3 lines that will be buried deep in the stack. You can even do it manually Gasp. and write the steps with screenshots in a word document or an email.
"lso first example runs locally on any computer with docker or podman or whatever installed, second example exclusively runs on AWS."
So we have a multiple GB full vendor neutral system that runs on any provider with support for a Free Operating system, or even your own machine. And you are getting hang up because the process for deploying that vendor neutral system is itself not vendor neutral?
This is what I was writing about getting hung up on the 1% last mile. It's going to draw so much effort to convert that last mile into a fully compliant vendor neutral solution, for almost no benefit, I just proved that you can port it in 3 seconds, if we migrate to GCP I just change the first line and you are done.
Furthermore as soon as you want to make this solution 100% compliant with whatever metric (in this case vendor neutrality), you introduce more dependencies with more stuff to make vendor neutral. In a sense you are now locked in to Docker, shouldn't we make an abstraction layer so that we can run this thing with Docker or Podman indistinguishably?
Get your focus back on the actual product you are building instead of how nice 3 lines look.
Besides the semantic usecases of Docker which can be infinite, technically docker is a virtualization and isolation mechanism. So whatever you do with docker can also be done with type 1, 2 virtualization or even processes and users (hint that's what docker is actually built on). There's plenty of junior programmers that learn to docker run something to isolate it without learning how to isolate with basic user permissions.
So the use case isn't really relevant when I say that you can live without docker.
In general if you ever find yourself complaining about your free stuff, I recommend that you uninstall it to show yourself you don't need it. And then you can reconsider to come back to it again from a place of gratefulness instead of demanding neediness.
Containers are not virtualisation.
> So whatever you do with docker can also be done with type 1, 2 virtualization
This statement is redundant. Whatever you do with docker can also be done with a Turing machine built using magic the gathering[1].
> There's plenty of junior programmers…
And there are plenty of junior programmers who think containers = virtualisation :)
https://en.wikipedia.org/wiki/Docker_(software)
>Docker is a set of platform as a service (PaaS) products that use OS-level virtualization to deliver software in packages called containers.[5]
https://lwn.net/Articles/179361/
>"Virtualization" is the act of making a set of processes believe that it has a dedicated system to itself.
>Full virtualization and paravirtualization are not the only approaches being taken, however. An alternative is lightweight virtualization, generally based on some sort of container concept.
https://people.freebsd.org/~bapt/pdfdocs/papers/jail.pdf
>To this end, we describe the newFreeBSD ‘‘Jail’’facility,which provides a strong partitioning solution, leveraging existing mechanisms, such as chroot(2), to what effectively amounts to a virtual machine environment.
> And there are plenty of junior programmers who think containers = virtualisation :)
At least we do agree on one thing, there is one and only one subpar engineer among us.
Indeed, the one who thinks containers are nothing but Docker.
Or better yet, the one who cites a PDF from 2000 or an article from 2006, both before ec2 even launched, to say virtualization is synonymous with containers as if the meaning hasn’t shifted since then…
Or, at the very least, the one who thinks “ssh apt-get install” is equivalent to a container image.
>Indeed, the one who thinks containers are nothing but Docker.
I just cited papers talking about jails, zones and chroot..
>to say virtualization is synonymous with containers
I said containers are virtualization, not that virtualization is synonymous with containers. That is container ∈ virtualization, not container = virtualization.
No offense but that's a highschool level reading comprehension error right there.
>Or better yet, the one who cites a PDF from 2000 or an article from 2006,
At least I cited stuff.
Go ahead and submit something to wikipedia with sources if you think containers are no longer virtualization.
Otherwise I'm out.