-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker-compose is pulling latest for many of the docker images #79
Comments
Will the current |
Yes. Right now we are verifying the stability of it and doing some optimizations to shrink the images and speed up boot times so it'll be a solid 1.0 to start from. |
Great. If there's a period of time where 1.0 and latest are identical, we
will have an opportunity to safely update learning center Katacoda
scenarios.
…On Fri, Mar 5, 2021 at 11:37 AM Aaron Kalin ***@***.***> wrote:
Will the current latest become 1.0?
Yes. Right now we are verifying the stability of it and doing some
optimizations to shrink the images and speed up boot times so it'll be a
solid 1.0 to start from.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#79 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APLSXFQOJODXXNBYEHRAYKDTCEXIBANCNFSM4YBJ67TA>
.
|
The good news is the image names are entirely different for these 1.0 versions so this issue is actually for the old images that are always latest and haven't been updated for a while. |
Once we can verify #89 across our training scenarios, we can stamp 1.0 and do a new pull request to use specific image versions. |
take a look at any of the docker-compose files. many of the images are set to pull latest. Can we go to a specific tag?
The text was updated successfully, but these errors were encountered: