The volumes definition in image spec is not very clear, but I assume it's expected behavior is similar with Dockerfile VOLUME.

Actually, we don't use docker volumes in Kubernetes. However, there may be user relying on image volumes (e.g. mongo:latest relies on volumes /data/configdb and /data/db). There are 2 options for volumes:

Volume directory and content should be in image already, we could ignore Volumes as what we are doing today. However, a problem with this is that if container rootfs is specified as read-only, the volume directories will be read-only, too. However, docker mounted these volumes as rw in that case. This will be a regression.
Do what docker does: create local file, copy volume content into the file, and mount the file into container as rw. There is no regression for this approach, but we need to add helper in containerd to do this, it will be similar with WithUserID or WithUsername which require pre-access to container root filesystem.

@ijc @crosbymichael Any opinions?

Support ExposedPorts and Volumes in image config. #186

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions