Overview: Support for Docker image Bootimus

Application Name: Bootimus
Web site : https://bootimus.com/
Application: https://github.com/garybowers/bootimus

Overview :

Modern PXE/HTTP Boot Server

A production-ready, self-contained PXE and HTTP boot server written in Go with embedded iPXE bootloaders, SQLite/PostgreSQL support, and a full-featured web admin interface. Deploy in seconds with a single binary or Docker container.

There Be Dragons!

This is an early-stage work-in-progress project - there may be bugs. Please raise an issue for any unexpected behaviour you encounter.

 

Make sure to look at the complete documentation

 

Please post any questions/issues relating to this docker template you have in this thread.

reserved

@ZappyZap thx a lot for creating the docker template and this thread!

Neat! Just removed iVentoy a few days ago because the image had never been rebuilt...

Might want to add vars for

BOOTIMUS_PROXY_DHCP_ENABLED
BOOTIMUS_WINDOWS_SMB_ENABLED

Probably defaulting to false.

In the unraid context it'll probably be often useful/necessary to run it on br0 e.g. if Pi-Hole is used (Pihole needs to be on br0, Bootimus needs to be able to talk to it but it can't when on bridge). br0 is also needed for BOOTIMUS_WINDOWS_SMB_ENABLED since otherwise it'd conflict with unraid's own samba.

Also usually not recommended to use --restart=always as that can create loops in case of bad config.

Edited April 24Apr 24 by Kilrah

@Kilrah thanks a lot i will add those
did i use --restart=always , that's was a mistake i usually use : --restart=unless-stopped

i will push an update tonight
Thanks Again

@ZappyZap really appreaciate your efforts regarding the template! This will push bootimus a lot.

I have now swapped to your template and noticed two things:

1. data directory: it contains all data like: db, bootloaders folder, ...
I think the default path should be "/mnt/user/appdata/bootimus" instead of "/mnt/user/appdata/bootimus/data".
Is there a reason for the seperate /data on the host?
Is it possible to change it?
Because the container is relatively young, a change today will not force to much users to chnage something in their configuration.

2. the logo provided by the template is too low in resolution.
Ex.: Emby docker has a logo resolution of 375x375 and bootimus 64x64
In the logos/ folder of the repo you can find higher resolution logos, like the "bootimus_logo_square_ulow.png" which is 256x256 pixel.

This is a great tool, thanks for the effort.

While I don't really use the templates, as I do everything in compose with DockGE, it made me discover a great replacement for iVentoy.

But is it just me, or are the docs down? Every page gives an error for me.

@bartdejonckheere yeah, also for me the github doc pages gives me an error. I think we have to wait until it gets fixed.
Maybe an github issue, if it's not solved soon, we can raise an issue on github.

17 minutes ago, pOpYRaid said:

@bartdejonckheere yeah, also for me the github doc pages gives me an error. I think we have to wait until it gets fixed.
Maybe an github issue, if it's not solved soon, we can raise an issue on github.

Good to know it's not just me. Yeah, let's wait and see. 🙂

Can always go read the files directly

https://github.com/garybowers/bootimus/tree/main/docs/en

Edited April 25Apr 25 by Kilrah

19 hours ago, pOpYRaid said:

@ZappyZap really appreaciate your efforts regarding the template! This will push bootimus a lot.

I have now swapped to your template and noticed two things:

1. data directory: it contains all data like: db, bootloaders folder, ...
I think the default path should be "/mnt/user/appdata/bootimus" instead of "/mnt/user/appdata/bootimus/data".
Is there a reason for the seperate /data on the host?
Is it possible to change it?
Because the container is relatively young, a change today will not force to much users to chnage something in their configuration.

The thinking behind have a directory in /mnt/user/appdata/bootimus is
all data go to data
if we want to add logs dir we coul easily
this have no impact on the container , it is where it mount on the host...

2. the logo provided by the template is too low in resolution.
Ex.: Emby docker has a logo resolution of 375x375 and bootimus 64x64
In the logos/ folder of the repo you can find higher resolution logos, like the "bootimus_logo_square_ulow.png" which is 256x256 pixel.

I will update that

Yeah, that's a good point. Have moved all data into the data directory, to be as close to the template as it could be.

Thanks for correcting the logo.

6 hours ago, pOpYRaid said:

Thanks for correcting the logo.

Logo should be updated now
keep the comment/feedback coming

thanks

Edited April 26Apr 26 by ZappyZap