Skip to content

Experimental live restore of containers doesn't work with systemd #21933

@tonistiigi

Description

@tonistiigi

Output of docker version:

Client:
 Version:      1.11.0-dev
 API version:  1.24
 Go version:   go1.5.3
 Git commit:   bb9b173
 Built:        Wed Apr  6 10:13:31 2016
 OS/Arch:      linux/amd64
 Experimental: true

Server:
 Version:      1.11.0-dev
 API version:  1.24
 Go version:   go1.5.3
 Git commit:   bb9b173
 Built:        Wed Apr  6 10:13:31 2016
 OS/Arch:      linux/amd64
 Experimental: true

Output of docker info:

Containers: 6
 Running: 0
 Paused: 0
 Stopped: 6
Images: 1
Server Version: 1.11.0-dev
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 14
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 4.2.0-34-generic
Operating System: Ubuntu 15.10
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.954 GiB
Name: vagrant-ubuntu-wily-64
ID: FWOL:PZYR:QW4F:45XN:3DKH:OD67:XT72:R6Z6:7FCS:34B5:JR4C:ZKUT
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 12
 Goroutines: 28
 System Time: 2016-04-11T17:27:15.522177616Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Experimental: true
Insecure registries:
 127.0.0.0/8

Steps to reproduce the issue:

  1. Start daemon with systemd
  2. Run a container
  3. Sigkill daemon
  4. On start container is not running

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugBugs are bugs. The cause may or may not be known at triage time so debugging may be needed.version/master

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions