4 ms·

Run your own registry.

baq 2y ago
This also applies to any package manager repository you might be using. JFrog charges loads of money for Artifactory, btw
- XorNot 2y ago
  There are plenty of open source registry implementations though, including just running "distribution" from Docker. The format is not hard to implement either for basic storage.
  - baq 2y ago
    The point is Artifactory has basically all popular (and some not very popular) repository format support built-in while supporting serious traffic, sharding, replication, etc. so you don't have to hunt for and then maintain anything. They've got a good tool, it's just expensive.
- marginalia_nu 2y ago
  Reposilite is a nice and easily deployed alternative.
TZubiri 2y ago
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...
- planb 2y ago
  We're not talking about Dockerfiles here, but about images from a registry. How many times faster and more reproducible is "docker run myimage:1.0.0" compared to your solution?
  - TZubiri 2y ago
    The thing with containerization is that it is sometimes used to virtualize an OS and sometimes to virtualize processes. My containerless worflow, when compared to typical container workflows, usually involves splitting some of the responsibilities to the OS virtualization layer and some to the process layer. For example, if I have a testing server and a prod server, to test a change I just git push to the testing branch. Which is quite fast and reproducible. Yes in theory there can be side effects and leftover effects from the previous version, but I am also a competent programmer and have the capacity to ssh into the server to debug, so it's not a huge issue. So bottomline I don't virtualize as often. To take a wildly different use case of containers, if I want to have two different systems on the same machine, I just run the two different systems as processes? You know there's a process for a sql db and an http server in the server and we are fine. You can even use users for more stringent encapsulation and security guarantees, it's fine. But since we are talking about registries, I focused on the third distinct use case deployment automation. The whole details on how to live without docker (and docker registries by extension) won't fit a hacker news comment, but be assured it's 100% possible and you'll be fine. I'm focusing on docker as a whole because if I can prove that you don't need Docker, by extension I prove you don't need a docker registry. It's an overkill of an argument to show how ridiculous complaining about your free docker registries is. You are out here complaining about a problem with your Docker registries, while I'm a chad who can just axe Docker like it's nothing.
    - planb 2y ago
      > The thing with containerization is that it is sometimes used to virtualize an OS and sometimes to virtualize processes. You can use any tool wrong - that does not make the tool obsolete. > The whole details on how to live without docker (and docker registries by extension) won't fit a hacker news comment An explanation how to do the same with docker WOULD fit in a hacker news comment. Sometim, abstractions are useful, even if they add another layer on top of existing stuff (and more dependencies).
aaomidi 2y ago
They do.

baq 2y ago

This also applies to any package manager repository you might be using. JFrog charges loads of money for Artifactory, btw

XorNot 2y ago
There are plenty of open source registry implementations though, including just running "distribution" from Docker. The format is not hard to implement either for basic storage.
- baq 2y ago
  The point is Artifactory has basically all popular (and some not very popular) repository format support built-in while supporting serious traffic, sharding, replication, etc. so you don't have to hunt for and then maintain anything. They've got a good tool, it's just expensive.
marginalia_nu 2y ago
Reposilite is a nice and easily deployed alternative.

TZubiri 2y ago

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...

planb 2y ago
We're not talking about Dockerfiles here, but about images from a registry. How many times faster and more reproducible is "docker run myimage:1.0.0" compared to your solution?
- TZubiri 2y ago
  The thing with containerization is that it is sometimes used to virtualize an OS and sometimes to virtualize processes. My containerless worflow, when compared to typical container workflows, usually involves splitting some of the responsibilities to the OS virtualization layer and some to the process layer. For example, if I have a testing server and a prod server, to test a change I just git push to the testing branch. Which is quite fast and reproducible. Yes in theory there can be side effects and leftover effects from the previous version, but I am also a competent programmer and have the capacity to ssh into the server to debug, so it's not a huge issue. So bottomline I don't virtualize as often. To take a wildly different use case of containers, if I want to have two different systems on the same machine, I just run the two different systems as processes? You know there's a process for a sql db and an http server in the server and we are fine. You can even use users for more stringent encapsulation and security guarantees, it's fine. But since we are talking about registries, I focused on the third distinct use case deployment automation. The whole details on how to live without docker (and docker registries by extension) won't fit a hacker news comment, but be assured it's 100% possible and you'll be fine. I'm focusing on docker as a whole because if I can prove that you don't need Docker, by extension I prove you don't need a docker registry. It's an overkill of an argument to show how ridiculous complaining about your free docker registries is. You are out here complaining about a problem with your Docker registries, while I'm a chad who can just axe Docker like it's nothing.
  - planb 2y ago
    > The thing with containerization is that it is sometimes used to virtualize an OS and sometimes to virtualize processes. You can use any tool wrong - that does not make the tool obsolete. > The whole details on how to live without docker (and docker registries by extension) won't fit a hacker news comment An explanation how to do the same with docker WOULD fit in a hacker news comment. Sometim, abstractions are useful, even if they add another layer on top of existing stuff (and more dependencies).

aaomidi 2y ago

They do.