Before the era of Dockers, we would include a ReleaseNotes.txt file with each package we delivered. Admittedly the user had to install the package first, but having installed it, the ReleaseNotes.txt file would be sitting there on their server where they could easily read it, without having to start up the application. Now, when we deliver a Docker image, the ReleaseNotes.txt file is included, but it’s inside the Docker container, which makes it considerably less convenient for users to access. Moreover, there isn’t a straightforward way to get at them that doesn’t imply starting the application.
Has anyone come up with a better mechanism or is there some industry norm on how to deal with this, i.e. make the release notes conveniently available to users, in particular before they run the container?
Yes, the user could create the container without starting it, and do something like “docker cp” to copy the release notes file out, and read it. But I think that’s asking too much of them.
Thanks for any suggestions