Re: [atomic-devel] resize container

I have successfully used the -v option. The problem is consistency. When moving from docker to boot2docker, depending on the host, I am running into file permission issues which I understand cannot be avoided. With this particular use case, I am currently restricted to a Linux host which has enough space available.

On Thu, Aug 6, 2015 at 1:54 PM, Matt Micene <nzwulfin gmail com> wrote:

Persistent storage for containers is usually either made available as a docker volume or with kubernetes persistent volumes.

Docker volumes (either direct or via a data container) are local directories on the host. You can add a new drive to the atomic host and use the -v option to make it visible in the container.

Kubernetes persistent volumes are a bit more complex and I'd suggest looking at the upstream docs.

I have a large database that exceeds 10GB

On Aug 6, 2015 11:20 AM, "Matt Micene" <nzwulfin gmail com> wrote:
Containers don't have filesysyems per se, but images are created as large as needed by the various commands in the Dockerfile.

Can you describe what you are doing that is running into space related issues in a container? Usually there's a need for volumes to be presented to a container for persistent or logging data etc.

Cheers
- Matt M

On Aug 6, 2015 6:47 AM, "Carl Mosca" <carljmosca gmail com> wrote:
Is it possible to resize a container's filesystem?

TIA,
Carl

--
Carl J. Mosca

Carl J. Mosca