Skip to content

Disable "zfs-volume-wait" service inside container #143

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

Merged
merged 1 commit into from
Sep 30, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
#
# During upgrade verification, the root filesystem will be booted as a
# container using systemd-nspawn. When the zfs-volume-wait service runs
# in this container, it will fail to complete in a timely manner,
# resulting in a failure to start the upgrade container (the logic that
# starts the container will timeout).
#
# The service fails to complete in a timely manner because "/dev" in the
# container is not the same as "/dev" on the host. The ZVOL devices that
# the service is waiting to appear in "/dev", will not appear within the
# container (by design).
#
# Thus, to workaround this problem, we explicitly disable this service
# from running when inside of the container.
#
[Unit]
ConditionVirtualization=!container