Skip to content

systemd cgroup scope somehow gets left behind not allowing containers to start #7015

Closed
@ibuildthecloud

Description

@ibuildthecloud

I ran into a situation in which I got:

[error] container.go:468 Error running container: Unit docker-d3ca1668bff4e74d22113886ba1433ecae920ece02c76ce1a9344409b68903bc.scope already exists.

It seems the scope did not get cleaned up by systemd. The scope file was still present in /run/systemd/system/... but systemd-cgls did not show it. In the end I had to delete the container because I couldn't start it.

The way I got into this situation is I had a container that would die on startup and I had a script that was auto-restarting it. So it was starting this container every 5 seconds and it would die every 5 seconds. Eventually it must have hit some race condition, and then it just started to always fail to start in docker because of this cgroup issue.

This is systemd 212 and docker 1.0.1 running CoreOS 367.1.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions