| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Change-Id: I84a2ad8d7b88e379ec282b0e57d99b76fe097375
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It turns out that `manage-baserock rm` can delete data from filesystems
that are mounted in a chroot directory. This is most likely to happen if
the chroot is active (and schroot created the mounts), so let's check
that there are no active sessions before deleting.
You now get a message like this if you try to remove a chroot with
active sessions:
I found the following active sessions for chroot '15.19':
session:baserock-15.19-4ef616d2-fdbf-4796-bcee-7132b989a2f8
session:baserock-15.19-e0f00498-190a-44be-9d29-cce057cbb259
You might lose data in mounted filesystems if I were to
recursively delete path /opt/baserock/chroots/15.19.
If you think these sessions are stale, you can run the
following command to end ALL schroot sessions:
schroot --end-session --all-sessions
I found that on my laptop there were a lot of stale sessions, probably
from when my computer had crashed while an 'schroot' session was open
so the session didn't get automatically ended. Stale sessions now will
prevent the user from being able to use `manage-baserock rm` so we need
to tell them about them.
Change-Id: I90aa19717d8e7007fb6aced9a8e9422967ddc64f
|
| |
|
|
| |
Change-Id: I8d3cf06cabf7fc2cae2fd9752bf288294787ce84
|
| | |
|
| |\
| |
| |
| | |
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It's slightly confusing that this script doesn't parse file:// URLs,
but this is an improvement.
Previously the error given was:
ln: failed to create symbolic link ‘/opt/baserock/chroots/tmp.P46u6ZxYQC/tarball’ -> ‘’: No such file or directory
Sorry, could not link foo into place
|
| | |
| |
| |
| |
| |
| |
| | |
Create the directory if missing to avoid this when doing
`manage-baserock add`
mktemp: failed to create directory via template ‘/opt/baserock/chroots/tmp.XXXXXXXXXX’: No such file or directory
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This is better than proceeding to add a system with a different name
to the one the user specified, without telling them that the name was
mangled.
|
| |/
|
|
| |
Baserock version numbers contain '.', so it's common to want to use it.
|
| |\
| |
| |
| | |
Reviewed-By: Lars Wirzenius <lars.wirzenius@codethink.co.uk>
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
Otherwise, weird errors occur when deploying to rawdisk:
Error creating disk image2014-06-10 16:00:40
[devel-system-x86_64-generic][my-raw-disk-image][rawdisk.write]Failure
to create disk image at /src/tmp/testdev.img
ERROR: Command failed: mount -o loop /src/tmp/testdev.img
/src/tmp/deployments/tmpQ7wXO1/tmp4lVDcu/tmpvHSzDE
mount: mounting /dev/loop0 on
/src/tmp/deployments/tmpQ7wXO1/tmp4lVDcu/tmpvHSzDE failed: Device or
resource busy
|
| |
|
|
|
|
|
|
|
|
| |
This adds a shared /src mounted from /opt/baserock/src
This allows chroots to share /src and also provides a persistent
src space in the face of adding and removing chroots.
Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
Reviewed-by: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| |\
| |
| |
| |
| | |
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| | | |
|
| |/
|
|
|
|
|
| |
The SSH authentication agent is supported by a pairing of a socket and an
environment variable. This patch ensures that no matter where the agent socket
might be, a new socket in /tmp (always shared with the chroot) is made and
forwarded into the chroot's environment via 'env'
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
