Pixiecore

Run pixiecore as a managed container, auto-configured to serve netboot.xyz to any host that netboots on the LAN. WHAT IT DOES

Runs the official pixiecore container (pixiecore quick xyz) as a long-lived service via @svendowideit/container-service. Any host that requests a netboot from the local network is offered the netboot.xyz iPXE menu, with no per-host configuration. The container runs on the host network stack (--network host) and listens on 0.0.0.0 (the pixiecore default listen address), so PXE/proxy-DHCP traffic reaches it.

INSTALL

swamp extension pull @svendowideit/pixiecore

DEPENDENCIES

@svendowideit/container-service (pulled automatically) and a container runtime (Docker, Podman, or Apple Containers) on PATH.

RUN

# Create and start the pixiecore service (idempotent).
swamp model create @svendowideit/pixiecore pixie \
  --global-arg binary=docker
swamp model method run pixie ensure

# Same, selecting a different image or listen port:
swamp model method run pixie ensure \
  --input image=pixiecore/pixiecore:master

# Inspect the running container.
swamp model method run pixie status

# Stop and remove the container.
swamp model method run pixie remove

CONFIGURE

Global arguments (set with --global-arg at model creation):

image          container image (default pixiecore/pixiecore:master)
containerName  container name (empty derives from the model name)
serviceBackend direct | systemd (default direct)
binary         docker | podman | container (default docker)
listenAddr     IPv4 address to listen on (default 0.0.0.0)
httpPort       HTTP port for the netboot payload (default 80)
statusPort     optional separate status port (default 0 = disabled)
dhcpNoBind     handle DHCP without binding (default true)
debug          enable pixiecore debug logging (default false)
restart        restart policy (default unless-stopped)

WHAT IT INSTALLS

A container (via @svendowideit/container-service). With serviceBackend systemd it also writes a user systemd unit. Nothing else is installed.