org.eclipse.che.plugin.docker.client.exception.DockerException: Error response from docker API, status: 400, message: client is newer than server (client API version: 1.20, server API version: 1.19)


Solutions on the web

Solution icon of github
Error response from docker API, status: 400, message: client is newer than server (client API version: 1.20, server API version: 1.19)

Solution icon of github
via GitHub by riuvshin
, 10 months ago
Error response from docker API, status: 500, message: Error response from daemon: no such file or directory

Solution icon of github
via GitHub by zaozaool
, 1 year ago
Error response from docker API, status: 404, message: Container command '/bin/sh' not found or does not exist.

Solution icon of github
Error response from docker API, status: 404, message: Container command '/bin/sh' not found or does not exist.

Solution icon of github
via GitHub by GJRTimmer
, 9 months ago
Error response from docker API, status: 404, message: stat /volume1/Docker/che/data/workspaces/wksp-oqjc: no such file or directory

Stack trace

org.eclipse.che.plugin.docker.client.exception.DockerException: Error response from docker API, status: 400, message: client is newer than server (client API version: 1.20, server API version: 1.19)
	at org.eclipse.che.plugin.docker.client.DockerConnector.getDockerException(DockerConnector.java:1304)[che-plugin-docker-client-4.6.2.jar:4.6.2]
	at org.eclipse.che.plugin.docker.client.DockerConnector.listContainers(DockerConnector.java:244)[che-plugin-docker-client-4.6.2.jar:4.6.2]
	at org.eclipse.che.plugin.docker.client.DockerConnector.listContainers(DockerConnector.java:218)[che-plugin-docker-client-4.6.2.jar:4.6.2]
	at org.eclipse.che.plugin.docker.machine.cleaner.DockerContainerCleaner.run(DockerContainerCleaner.java:61)[che-plugin-docker-machine-4.6.2.jar:4.6.2]
	at org.eclipse.che.commons.schedule.executor.LoggedRunnable.run(LoggedRunnable.java:43)[che-core-commons-schedule-4.6.2.jar:4.6.2]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[na:1.8.0_92-internal]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[na:1.8.0_92-internal]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[na:1.8.0_92-internal]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[na:1.8.0_92-internal]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[na:1.8.0_92-internal]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[na:1.8.0_92-internal]
	at java.lang.Thread.run(Thread.java:745)[na:1.8.0_92-internal]

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.