Estimated Time of Arrival is arguably more useful than elapsed time, in the section where the Docker CLI indicates ongoing layer transfers.
Smart idea!
Here is the thing: most paying Docker customers probably use build pipeline, so they would never see such a feature.
Therefore the resources of Docker company are probably not put on such a topic.
The great thing about Docker is that it is open source, so you can implement the feature yourself (or hire a third party) and do a pull request to the source.
You’re forgetting local builds.
Even when CI/CD exists, engineers have a need to build locally. It would be a terribly slow workflow to only ever tinker on CI/CD. And local is needed as an option during occasional CI/CD outages.
Submit a feature request on Moby Github. But personally I don’t think someone will take the time and implement this.
Do you have an idea how it could be calculated? The elapsed time is something you can an information to use after the build process ends, so you know what took long and where you should probably optimize.
I would be happy to see an estimated time that tells me when the build will be fnished, but I have no idea how it could be estimated. It depends on so mny things and anything could be in any layer. When it is about copying a file, that is probably estimatable, but when you execute a command in a RUN instruction, that is probably not. Unless the command itself that you execute knows about itself and shows an estimated time.
Maybe the Docker developers have some ideas, but they will see it more likely if you share it in the roadmap
To clarify, I’m not asking for uncached Dockerfile directives to provide time estimates. Agreed, that would be impossible to implement reliably.
I’m asking specifically for cached layers, such as those stored on a registry, to provide download estimates .That’s something that even simple static file servers provide when properly configured.
Thanks for the clarification. That would probably be doable as webbrowsers do it too. The elapsed time would still be useful for CI/CD, but a flag or option to chosee between the two behavior or showing both could be a way to do it.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.