-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Error response from daemon: client is newer than server (client API version: 1.23, server API version: 1.22) #1636
Comments
Yes. I know the reason why this issue is caused. There have an inconsistent requirement between the official document (>=1.8) and the official docker image (== latest). It's a point for me. IMO,the better way is to fix description in |
@monaka Those requirements are to run Che as a server. Indeed, running it as a Docker container may cause such issues with host and container Docker versions incompatibility. I'll add some notes to docs. |
@monaka you may try the new installer https://eclipse-che.readme.io/docs/usage-docker-launcher? |
@monaka - we look forward to your feedback on the new installer. One of the things this does is to launch Che from within a container. So it lets us standardize the client that is invoking Che into a container that works the same on everyone's computer. So this issue should go away. We are still making some improvements, but it is largely stabilized now. |
@eivantsov @TylerJewell , I checked your new installer. My first impression is 👍 🍣. |
Thanks for the feedback! |
Docker container requires newer version of Docker daemon than described at Prereq
Reproduction Steps:
docker run
same as description on Usage: DockerExpected behavior:
The container runs.
Observed behavior:
che.sh failed with this message.
[Describe observed behavior here]
Che version: 4.4.0. Image digest is sha256:740fe2bd7a325588031882bcee517d49baac9c68e2d4d2e92397cf386985e6c0.
OS and version: CoreOS 1010.6.0 (MoreOS)
Docker version: 10.0.3
Che install: Docker container
Additional information:
The text was updated successfully, but these errors were encountered: