New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move container volume between different pools on local machine #4847

msjyoo opened this Issue Jul 29, 2018 · 2 comments


2 participants
Copy link

msjyoo commented Jul 29, 2018

Required information

  • Distribution: bionic
  • Distribution version:
  • The output of "lxc info" or if that fails:
    • Kernel version: 4.15.0-29-generic
    • LXC version: 3.0.1
    • LXD version: 3.0.1
    • Storage backend in use: btrfs

Issue description


I'm trying to resize my lxd container that has run out of disk space that is using the default btrfs backend, but I cannot find a way to do so. I've tried to move the container volume from the default to a newly-created larger volume, but it seems container volumes cannot be moved.

Is this a missing feature (container volumes can't be moved) or am I expected to use another workflow to resize a btrfs container that's out-of-space?

Steps to reproduce

  1. lxc storage volume move default/seedbox default2/seedbox
DBUG[07-29|17:56:04] Sending request to LXD                   etag= method=GET url=http://unix.socket/1.0/storage-pools/default/volumes/custom/seedbox
Error: not found

This comment has been minimized.

Copy link

msjyoo commented Jul 29, 2018

I've manually modified the btrfs loopback image using truncate and btrfs filesystem resize. However, the configuration seems unchanged when I use lxc storage show default. Am I correct in guessing that the size value in the config is for creation only, and is purely cosmetic?


This comment has been minimized.

Copy link

stgraber commented Jul 29, 2018

Yeah, it's purely cosmetic. We do have support for moving storage volumes between pools in LXD 3.2.

@stgraber stgraber closed this Jul 29, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment