Closed eclake closed 7 years ago
Docker latest tag applied to 0.3.5 so docker pull and docker run should use latest version by default from now on
Great! :)
Didn't seem to have attached to correct version - will figure out and re-push but re-opening for now
This is solved by now, isn't it?
I'm pretty sure it is... is the beagle version info in v0.5.8? If so I can check definitively!
Not yet. This an important thing (being able to get the version), but we should think about a way of making it automatic... It's very prone to errors having to manually change a line of code every time a new release is made...
We can further discuss this on jacopo-chevallard/BEAGLE#124
As you were suggesting, I convinced myself that it's safer to oblige users to pull a tag (i.e. a version) explicitly, hence removing the latest
tag from the available Docker-Beagle tags.
At this point, pulling from beagletool/beagle
without specifying any tag, i.e. using the command docker pull beagletool/beagle
, triggers the error
Using default tag: latest
Pulling repository docker.io/beagletool/beagle
Tag latest not found in repository docker.io/beagletool/beagle
Shall we leave it like this, and use a (e.g. weekly) mailing list to provide Beagle users updates about the available versions?
Closing this, as stated above docker pulls of Beagle must specify a tag
I didn't realise, but now know that I have to set the latest tag, which is used as the default version for all docker pull and docker run commands, by hand.
Am moving latest tag to the v0.3.5 image now and will close this issue once it has been successfully pushed to dockerHub.