{% extends "layout.html" %} {% block title %}{{ entry.name }} - Catalog - pixie{% endblock %} {% block subnav %} {% endblock %} {% block content %} {% if warn_update %}
{{ entry.name }}
(sha {{ entry.content_sha256[:12] }}) is
referenced by:
{% if blob_using_machines %}
{{ mac }}{{ name }}oras:// tag pointing at new bytes) the new
content will land at a new content-address and the machines /
exports above will still be pinned to the OLD sha until you
re-bind them. Point those machines at the new binding first, or
click "Update anyway" to overwrite.
{{ entry.name }}
(sha {{ entry.content_sha256[:12] }})
are referenced by:
{% if blob_using_machines %}
{{ mac }}{{ name }}{{ entry.name }} orphans the fetched netboot bundle
{{ orphans_bundle_name }}. The bundle stays on disk but no
disk-image entry will point at it -- nbdboot for this image will not work
until you either restore this entry or delete the bundle too.
{{ entry.name }} breaks nbdboot for
{{ breaks_nbdboot_for|length }} disk image{{ 's' if breaks_nbdboot_for|length != 1 else '' }}
that name{{ '' if breaks_nbdboot_for|length != 1 else 's' }} it as
netboot_src:
{{ name }}{{ entry.name }}
{{ entry.description }}
{% else %}No description recorded. {% if not entry.bindable %} Netboot bundles are usually the sibling of a disk-image entry; see below for the pairing. {% endif %}
{% endif %}{{ entry.src }}{{ entry.netboot_src }}{{ entry.content_sha256 }}
Not currently exported. An NBD export is spawned automatically when a machine
is bound to boot_mode=nbdboot pointing at this entry.
{{ export.name }}
No catalog entry matches {{ entry.netboot_src }}.
Import the sibling bundle to enable nbdboot for this disk image.
Nbdboot for {{ entry.name }} chains into this bundle's kernel + initrd:
{{ netboot_sibling.name }}
Every disk image that names {{ entry.src }} as its
netboot_src boots with this bundle's kernel + initrd.
{{ e.name }}
No disk-image entry names this bundle as its netboot_src yet.