5 ms·

The images you mention (alpine, node, golang) are all so-called “Docker Official Images”. Those are all the ones without a slash as the namespace separator in t

The images you mention (alpine, node, golang) are all so-called “Docker Official Images”. Those are all the ones without a slash as the namespace separator in them: https://hub.docker.com/search?q=&type=image&image_filter=official https://hub.docker.com/search?q=&type=image&image_filter=off... They are versioned and reviewed here: https://github.com/docker-library/official-images https://github.com/docker-library/official-images I don't expect them to go away. Disclosure: I maintain two of them (spiped, adminer).

karamanolev 4y ago
Useful information, bad look for Docker - "Oh, no slash as the namespace separator. Good and easy way to tell, that's how I would've done it!".
- cshimmin 4y ago
  I mean, it's not a terrible convention. On the website they have a badge ("docker official image"), but devs aren't usually looking at the website, they're looking at their Dockerfile in vim or whatever. This is a straightforward way to communicate that semantically through namespacing. Still, shame on docker for the rug-pull.
  - zamnos 4y ago
    It's better than none, but explicit over implicit. If it were namespaced like PULL docker.org/offical/alpine:latest that would be better, imo.
    - _cenw 4y ago
      They are also available at docker.io/library/alpine and equivalent, and I'd advise anyone to start using this format as more distros might break the default registry[1]. [1]: https://man.archlinux.org/man/containers-registries.conf.5.en#NOTE:_RISK_OF_USING_UNQUALIFIED_IMAGE_NAMES https://man.archlinux.org/man/containers-registries.conf.5.e...
legohead 4y ago
"don't expect" or "for certain"? Can't really plan ahead without some kind of certainty.
- Strom 4y ago
  There is no real distinction between those two phrases here, because the person using those phrases isn't ultimately in control.
  - stingraycharles 4y ago
    One could argue that only the person who is in control could say “for certain”, and as such, that is the implicit differentiator between those two phrases.
    - zamnos 4y ago
      I mean yeah okay fine the phrase is then "according to your understanding of the rules set forth by Docker, as of today's edit of the linked PDF (2023-03-15), and in accordance with the current (2023-03-15) configuration of the three images, `alpine`, `node`, and `golang`; are those three images covered by the open source program and will continue to be accessible or will those images cease to be accessible by non-paying members of the general public in thirty (30) days?" It's just that I'd thought we'd moved past the need for that level of pedantry here, but apparently not.
      - deleted 4y ago
        [deleted]
      - stingraycharles 4y ago
        I may sound pedantic, but in all honesty, Docker has been quite hostile over the past few years in terms of monetizing / saving costs, so nothing would surprise me at this point. I would definitely not feel comfortable saying "for certain". Phrased differently, if the person who is in control says "for certain", vs. some random HN user, I would attach a lot more value to the statement made by the personal in control.
_cenw 4y ago
One should get in the habit of prefixing them with docker.io/library through, simply because docker's claim on being the default namespace is unacceptable (and also not true on RHEL-adjacent distros)

karamanolev 4y ago

Useful information, bad look for Docker - "Oh, no slash as the namespace separator. Good and easy way to tell, that's how I would've done it!".

cshimmin 4y ago
I mean, it's not a terrible convention. On the website they have a badge ("docker official image"), but devs aren't usually looking at the website, they're looking at their Dockerfile in vim or whatever. This is a straightforward way to communicate that semantically through namespacing. Still, shame on docker for the rug-pull.
- zamnos 4y ago
  It's better than none, but explicit over implicit. If it were namespaced like PULL docker.org/offical/alpine:latest that would be better, imo.
  - _cenw 4y ago
    They are also available at docker.io/library/alpine and equivalent, and I'd advise anyone to start using this format as more distros might break the default registry[1]. [1]: https://man.archlinux.org/man/containers-registries.conf.5.en#NOTE:_RISK_OF_USING_UNQUALIFIED_IMAGE_NAMES https://man.archlinux.org/man/containers-registries.conf.5.e...

legohead 4y ago

"don't expect" or "for certain"? Can't really plan ahead without some kind of certainty.

Strom 4y ago
There is no real distinction between those two phrases here, because the person using those phrases isn't ultimately in control.
- stingraycharles 4y ago
  One could argue that only the person who is in control could say “for certain”, and as such, that is the implicit differentiator between those two phrases.
  - zamnos 4y ago
    I mean yeah okay fine the phrase is then "according to your understanding of the rules set forth by Docker, as of today's edit of the linked PDF (2023-03-15), and in accordance with the current (2023-03-15) configuration of the three images, `alpine`, `node`, and `golang`; are those three images covered by the open source program and will continue to be accessible or will those images cease to be accessible by non-paying members of the general public in thirty (30) days?" It's just that I'd thought we'd moved past the need for that level of pedantry here, but apparently not.
    - deleted 4y ago
      [deleted]
    - stingraycharles 4y ago
      I may sound pedantic, but in all honesty, Docker has been quite hostile over the past few years in terms of monetizing / saving costs, so nothing would surprise me at this point. I would definitely not feel comfortable saying "for certain". Phrased differently, if the person who is in control says "for certain", vs. some random HN user, I would attach a lot more value to the statement made by the personal in control.

_cenw 4y ago

One should get in the habit of prefixing them with docker.io/library through, simply because docker's claim on being the default namespace is unacceptable (and also not true on RHEL-adjacent distros)