DietPi

[joebowbeer]

Search results led me to believe that dietpi would be a good fit for pipedal on RPi 4/5.

I see a few dietpi mentions in issues and discussions in this repo, and I think it might be helpful to mention it in the docs as well.

Two issues I ran into are:

1. Auto-Hotspot disabled because NetworkManager is not used
2. avahi-daemon.conf file not found

dietpi@DietPi:~$ pipedalconfig --install
Configuring pipedal
Warning: The current OS is not using the NetworkManager network stack.
   The PiPedal Auto-Hotspot feature will be disabled.

   Consult PiPedal documentation to find out how to correct this
   issue on Ubuntu Server.
Warning: Unabled to disable Ipv6 mDNS announcements. File not found: "/etc/avahi/avahi-daemon.conf"
Error: Failed to start the pipedald service.
      Run 'pipedalconfig --install' again to complete setup of PiPedal.
PiPedal web server is listening on port 80

The second problem was solved by installing avahi-daemon:

sudo apt install avahi-daemon

Note: The dietpi.txt auto config script can be edited so that avahi-daemon (and alsa-utils) are installed automatically.

After that, and running pipedalconfig --install again, the pipedal server can be reached at http://dietpi.local/

I'm not sure what to do about the hotspot issue.

I think the options are:

1. Install DietPi's built-in hotspot tool (via dietpi-software) and do not use NetworkManager
2. Switch to NetworkManager

A disadvantage of DietPi's built-in hotspot is that there is not an easy way to configure it to start conditionally.

[rerdavies]

There are multiple network stacks on Linux. The auto-hotspot feature runs on only one of them. Raspberry Pi Os, and Ubuntu desktop use the right one. Ubuntu Server uses the other one (and the auto-hotspot connection is disabled). See this page (at the bottom) for how one goes about switching network stacks on Ubuntu Server. https://rerdavies.github.io/pipedal/Ubuntu.html If dietpi is debian-based, it's possible that the Ubuntu instructions might work for you too. Back everything up first (if applicable). Expect disaster. :-)

…

On Sat, Jul 4, 2026 at 8:07 PM Joe Bowbeer ***@***.***> wrote: Search results led me to believe that dietpi would be a good fit for pipedal on RPi 4/5. I see a couple dietpi mentions in issues and discussions in this repo, and I think it might be useful to mention it in the docs. Two issues I ran into are: 1. Auto-Hotspot disabled because NetworkManager is not used 2. avahi-daemon.conf file not found ***@***.***:~$ pipedalconfig --installConfiguring pipedalWarning: The current OS is not using the NetworkManager network stack. The PiPedal Auto-Hotspot feature will be disabled. Consult PiPedal documentation to find out how to correct this issue on Ubuntu Server.Warning: Unabled to disable Ipv6 mDNS announcements. File not found: "/etc/avahi/avahi-daemon.conf"Error: Failed to start the pipedald service. Run 'pipedalconfig --install' again to complete setup of PiPedal.PiPedal web server is listening on port 80 The second problem was solved by installing avahi-daemon: sudo apt install avahi-daemon Note: The dietpi.txt auto config script can be edited so that avahi-daemon (and alsa-utils) are installed automatically. After that, and running pipedalconfig --install again, the pipedal server can be reached at http://dietpi.local/ I'm not sure what to do about the hotspot issue. I think the options are: 1. Install DietPi's built-in hotspot tool - Run dietpi-software - To avoid conflicts, do not use NetworkManager for your network setup 2. Switch to NetworkManager A disadvantage of DietPi's built-in hotspot is that there is not an easy way to configure it to start conditionally. — Reply to this email directly, view it on GitHub <#524?email_source=notifications&email_token=ACXK2DEGSOYL5QUCXNRWH235DGL4DA5CNFSNUABBM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPGEYDGNZRGU2DNJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACXK2DHQNW5D5AYYHSLKZ5D5DGL4DAVCNFSNUABIKJSXA33TNF2G64TZHMZTSNRTHE4DGNJTHNCGS43DOVZXG2LPNY5TCMBTG4YTKNBWUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ACXK2DB3CLNED4XA2Q3OGPD5DGL4DA5CNFSNUABBM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPGEYDGNZRGU2DNJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/ACXK2DF65BRI2RF7QKI7NQL5DGL4DA5CNFSNUABBM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPGEYDGNZRGU2DNJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[spDuchamp]

I was able to get PiPedal auto-hotspot working on a fresh DietPi install using...

apt remove ifupdown
apt install network-manager polkitd pkexec dnsmasq

However, what I ended up doing was skipping the auto-hotspot stuff, did a fresh DietPi install and attached a cheap small but really wide HDMI touchscreen plugged into an Intel NUC with a USB audio interface. I set DietPi to auto-start to Chromium in kiosk mode to load http://127.0.0.1/ and it works really well. Had to do a little change to /boot/dietpi.txt to get the resolution right, and there was some futzing around with some startup stuff to defer network loading to get the boot time really fast.

[rerdavies]

fwiw, I don't *think* that the network manager interactions slow down the availability of the web server, although it is true that the list of available ports doesn't display until setup of the Auto-Hotspot is completed (since that message may optionally display an IP address for the hotspot connection). I'm pretty sure that the webserver starts running pretty much right away (after scanning for plugins has completed), and doesn't have to wait for the Auto-Hotspot at all.

…

On Mon, Aug 24, 2026 at 1:34 AM Stefan Powell ***@***.***> wrote: I was able to get PiPedal auto-hotspot working on a fresh DietPi install using... apt remove ifupdown apt install network-manager polkitd pkexec dnsmasq However, what I ended up doing was skipping the auto-hotspot stuff, did a fresh DietPi install and attached a cheap small but really wide HDMI touchscreen plugged into an Intel NUC with a USB audio interface. I set DietPi to auto-start to Chromium in kiosk mode to load http://127.0.0.1/ and it works really well. Had to do a little change to /boot/dietpi.txt to get the resolution right, and there was some futzing around with some startup stuff to defer network loading to get the boot time really fast. — Reply to this email directly, view it on GitHub <#524?email_source=notifications&email_token=ACXK2DHKIAO3AWG7M5H2TWL5LPHXBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGMYDMNZYUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18130678>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACXK2DFZTPCMZCEUYARGVHT5LPHXBAVCNFSNUABIKJSXA33TNF2G64TZHMZTSNRTHE4DGNJTHNCGS43DOVZXG2LPNY5TCMBTG4YTKNBWUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ACXK2DFO5YENUKVFIMPQL5L5LPHXBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGMYDMNZYUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/ACXK2DGGRGIPZDLAU5XMDRT5LPHXBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGMYDMNZYUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you commented.Message ID: ***@***.***>

[deberman]

I don't know if this is the proper place to report this but anyway. I set up pipedal/DietPi on a Rasperry Pi 4 yesterday and wanted to reduce boot time so I set static IP and disabled IPv6. Cut boot time in half but even better; Disabling IPv6 let me go from 128/4 to 16/4 buffer size. Hope that helps anyone.
Edit to add that this is of course depending on the patch.

[rerdavies]

@deberman:

That's pretty remarkable! Do you have any idea why?

[deberman]

No, my guess is it’s interrupting and that’s why I wanted to see if I could gain performance by turning it off. I did verify by enabling IPv6 again and got xruns.