4 ms·
That's a very good argument, but people have down used to dropping the domain prefix because it's always been optional. Giving people the option to configure a
by ffsm8 2y ago
That's a very good argument, but people have down used to dropping the domain prefix because it's always been optional.
Giving people the option to configure a default repository via the daemon.json would alleviate that issue, but I'm not sure if that's really enough to fork.
- hedora 2y agoThey’ve been betting it’s not for about ten years. With these changes, I can imagine “intro to docker” tutorials breaking. I suspect that’ll be enough to let a fork/competitor gain significant market share.
- theamk 2y agohm.. switch to fork just to avoid trivial, mechanical, 10-character change in docs and scripts? (image/name -> my-repo.com/image/name) I doubt it.
- DangitBobby 2y agoThe web is absolutely littered with docker tutorials and a huge proportion of them (not operated or maintained by docker themselves) would no longer be valid, I'm sure.
- jjfanboy 2y agoOh great, so now it's a hidden default that might be different system-to-system. Disjoint from the actual deployment config. Please, dear god, no. I'm sorry, this is a bad idea. It's just not that hard to go fully qualified.
- sodality2 2y agoIf you specify the fully qualified image location then it's irrelevant. It's only when you decide to use short hand that it comes into concern