Skip to content

getContainerConfig() is null when docker storage is overlayfs #1008

@lancechant

Description

@lancechant

Describe the bug
With new fresh installs of docker, the new storage default is overlayfs, instead of the deprecated overlay2 source This causes getContainerConfig to throw a null pointer exception

To Reproduce
Freshly install the latest docker version, and try run intergration tests with microshed, this causes the null pointer to happen, updating the docker daemon.json at /etc/docker/daemon.json with

{
    "storage-driver": "overlay2",
    "features": {
      "containerd-snapshotter": false
    }
  }

Allows it to use the old storage, and enables the IT's to work again

Expected behavior
For it to not throw a null pointer when using newer versions of docker storage

System information:

  • OS: [Windows, WSL(Ubuntu)]
  • Java Version: [11, 17]
  • MicroShed Testing Version: [e.g. 0.9.2]

Additional context
From my research an option is to swap from getContainerConfig to getConfig should work, but unsure, happy to test if there is a beta release to confirm

Metadata

Metadata

Assignees

No one assigned

    Labels

    is:bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions