Skip to content

Allow drive paths already in the jailer rootfs#510

Open
bduffany wants to merge 1 commit into
firecracker-microvm:mainfrom
bduffany:jailer-hardlink-fix
Open

Allow drive paths already in the jailer rootfs#510
bduffany wants to merge 1 commit into
firecracker-microvm:mainfrom
bduffany:jailer-hardlink-fix

Conversation

@bduffany
Copy link
Copy Markdown
Contributor

Before, when providing a drive which is already in the jailer
rootfs, the LinkFilesHandler would fail trying to hard-link the
file to the path where it is already linked.

This commit makes it so that we skip the hard-link step in this case.

This change allows provisioning virtual drive contents via FUSE, so
that the drive contents can be lazily fetched from a remote server.
The FUSE mount needs to be set up in the chroot ahead of time,
because FUSE files can't be hard-linked across filesystem boundaries.

Before, when providing a drive which is already in the jailer
rootfs, the LinkFilesHandler would fail trying to hard-link the
file to the path where it is already linked.

This commit makes it so that we skip the hard-link step in this case.

This change allows provisioning virtual drive contents via FUSE, so
that the drive contents can be lazily fetched from a remote server.
The FUSE mount needs to be set up in the chroot ahead of time,
because FUSE files can't be hard-linked across filesystem boundaries.

Signed-off-by: Brandon Duffany <brandon@buildbuddy.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant