c0d56ab717
When the daemon restores containers on daemon restart, it syncs up with containerd to determine the existing state. For stopped containers it then removes the container metadata from containerd. In some cases this is not handled properly and causes an error when someone attempts to start that container again. In particular, this case is just a bad error check. Signed-off-by: Brian Goff <cpuguy83@gmail.com> |
||
---|---|---|
.. | ||
client_daemon.go | ||
client_daemon_linux.go | ||
client_daemon_windows.go | ||
client_local_windows.go | ||
errors.go | ||
process_windows.go | ||
queue.go | ||
queue_test.go | ||
remote_daemon.go | ||
remote_daemon_linux.go | ||
remote_daemon_options.go | ||
remote_daemon_options_linux.go | ||
remote_daemon_windows.go | ||
remote_local.go | ||
types.go | ||
types_linux.go | ||
types_windows.go | ||
utils_linux.go | ||
utils_windows.go | ||
utils_windows_test.go |