** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510511
Title:
machinectl pull-raw fails: No space left on device
To manage
Apparently this will never get fixed upstream:
From
https://github.com/systemd/systemd/issues/5859#issuecomment-553377937
poettering: "So we dropped the automatic btrfs loopback file support in
machined a while back. Let's close this hence."
** Bug watch added:
This effects me on a brand new Ubuntu Server 18.04.3 Install
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510511
Title:
machinectl pull-raw fails: No space left on device
To manage notifications
marble@bravo:~$ sudo machinectl pull-tar
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-root.tar.gz
Enqueued transfer job 1. Press C-c to continue download in background.
Pulling
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510511
Title:
I tried that command (on current xenial, you didn't specify an Ubuntu
release/package version), and it works fine:
$ machinectl pull-raw
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img
Download of
Comment #1 specifies release, and package version (wily, release).
The disk space error I presume is of /var/lib/machines, which is managed
by the systemd-machined entirely. It is a loop mounted btrfs file, which
systemd should be automatically growing to correctly accommodate
increases in the
wily, 225-1ubuntu9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510511
Title:
machinectl pull-raw fails
To manage notifications about this bug go to:
