my partner, across the room: you know, they actually advise against cleaning the rollers with a q-tip while they spin because it could get caught in the mechanism
me, cleaning my partner's camera with a q-tip while the rollers spin, sucking all the fuzz into the mechanism: oh huh, good to know
![screenshot of the following dockerfile:
FROM debian:trixie AS cephwrap
RUN apt-get update && apt-get install -y curl
RUN curl -LO https://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img
RUN apt-get install -y qemu-system-x86 cloud-image-utils iproute2
RUN qemu-img resize noble-server-cloudimg-amd64.img +10G
COPY ./user-data ./user-data
COPY ./meta-data ./meta-data
COPY ./vendor-data ./vendor-data
COPY ./network-config ./network-config
COPY <<EOF ./run.sh
#!/bin/bash
set -ex
# a bunch of kerfuffle to put the vm directly on the network:
# - steal eth0's ip and assign it to the vm
# - create a bridge between eth0 and tap0
IP=\$(ip -o -f inet addr show eth0 | awk '{print \$4}')
IP_NO_MASK=\${IP%/*}
GATEWAY=\$(ip route | awk '/default/ {print \$3}')
sed -i "s|{{ADDRESS}}|\$IP|g" network-config
sed -i "s|{{ADDRESS}}|\$IP_NO_MASK|g" user-data
sed -i "s|{{GATEWAY}}|\$GATEWAY|g" network-config
cloud-localds cloud-init.iso user-data meta-data --vendor-data vendor-data --network-config network-config
ip link add br0 type bridge
ip tuntap add dev tap0 mode tap
ip link set tap0 master br0
ip link set tap0 up
ip addr del \$IP dev eth0
ip link set eth0 master br0
ip link set br0 up
qemu-system-x86_64 -machine accel=kvm,type=q35 -cpu host -smp 2 -m 2048 -drive file=noble-server-cloudimg-amd64.img,if=virtio -cdrom ./cloud-init.iso -display none -serial stdio -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -device virtio-net-pci,netdev=net0
EOF
CMD ["bash", "run.sh"]](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:r2p7kytjuidhmvsutbawfai7/bafkreifopjanc3aoij2ktyziqsdlokmeoacsd22sajjgfanqyk5stzhdki)
