Skip to content

Containerd content store is not accessible on macOS #199

@malt3

Description

@malt3

Image loading via docker load is slow (not incremental), so we recommend to users to make the containerd socket available to the image loader.
This way, the containerd content store can be used (if available).
On macOS, the containerd socket lives inside a Linux virtual machine, so it's not easily accessible from the host.

Docker is working on a feature to expose the content store directly on the docker socket, which will solve this problem on macOS at some point.
Meanwhile, I suggest either sticking to the (less performant) docker load fallback or using workarounds to proxy access to the containerd socket.

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