Please clarify that this is for Linux containers

[jasonbivins]

File: engine/reference/commandline/checkpoint.md

on my Windows environment, i get this error message when using Windows containers
Tested with both CE and EE versions

C:\Users\DockerJ>docker checkpoint create Tester checkpoint1 Error response from daemon: Cannot checkpoint container Tester: Windows: Containers do not support checkpoints

[gbarr01]

@jasonbivins , two questions:

• Are you using API version 1.25 or higher? Run docker version.
• Do you have experimental set to true? See https://docs.docker.com/docker-for-windows/#daemon

My guess is that you have experimental set to off. See the top of the checkpoint page for caveats.

[jasonbivins]

@gbarr01 I checked that before I posted :)

Clien:
 Version:       17.06.2-ee-11
 API version:   1.30
 Go version:    go1.8.7
 Git commit:    06fc007
 Built: Thu May 17 06:14:39 2018
 OS/Arch:       windows/amd64

Server:
 Engine:
  Version:      17.06.2-ee-11
  API version:  1.30 (minimum version 1.24)
  Go version:   go1.8.7
  Git commit:   06fc007
  Built:        Thu May 17 06:17:26 2018
  OS/Arch:      windows/amd64
  Experimental: true

[gbarr01]

Off the top of my head, if you are using Command Prompt, try PowerShell instead (but not ISE).

[gbarr01]

Oh hang on, I see. You are using Windows containers. Sorry about that. I need to think about how best to handle the docs. Editing the CLI reference docs is probably not the best solution.

Ps. I would still use PowerShell though ...

[jasonbivins]

Is there a better place to send requests like this?

[gbarr01]

Not necessarily. We need to clarify CLI limitations (if they exist) for Windows containers. But if you need help now, you could ask on the Docker forums or Stackoverflow, of course.

[gbarr01]

@thaJeztah , @gtardif , do you know about CLI limitations for Windows containers?

[thaJeztah]

In this case, it's an experimental feature that uses CRIU, which is a Linux only feature.

Not related to the Windows side of things, but checkpoint/restore currently has some issues due to the migration to containerd, and will get a major overhaul in future.

What should be done though, is that the CLI hides these commands if the daemon is running on Windows; I think we do so for some other commands (likely we didn't do that yet when this feature was implemented)

[thaJeztah]

Opened docker/cli#1094 to address this

[ghost]

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked