-
Notifications
You must be signed in to change notification settings - Fork 120
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
Add in M9 docs info about docker versions #1365
Comments
@riuvshin - you need to make sure and give it labels so it can be tracked. |
This is for the runbook. I'll take this. |
@riuvshin - you say this is needed for codenvy on puppet, but 5.0 will only ship with dockerized codenvy. Can you confirm that this PR and update to Docker is also part of Dockerized codenvy? |
@bmicklea in dockerized codenvy we don't install docker we just require it be installed and properly configured. |
Good - that's what I wanted to confirm. The description says "codenvy based on puppet" so I was confused... |
we did changes to puppet based codenvy and due to those changes Tyler asked us to add docs for dockerized codenvy |
got it, thanks
…On Mon, Dec 19, 2016 at 1:56 PM, Roman Iuvshin ***@***.***> wrote:
we did changes to puppet based codenvy and due to those changes Tyler
asked us to add docs for dockerized codenvy
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1365 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHSnCqZRKtZKv3-jkCctZSooAlCySEJpks5rJtNSgaJpZM4LPQx4>
.
--
Brad Micklea | bmicklea@codenvy.com | 416.707.0792
|
PR is: eclipse-che/che-docs#62 |
here we have PR which will update docker to 1.12.5 in codenvy based on puppet https://github.com/codenvy/deployment/pull/163
this is needed to get rid of bug in docker #1164
but for codenvy in docker we have to write some info in docs that will tell users that if they will be using 1.11.x docker they may run in to that issue.
@TylerJewell please assign to this issue some one who is able to do that.
The text was updated successfully, but these errors were encountered: