-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Internal TFTP server fails to start after version 0.7.1-ls173 #70
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Reverting to a previous version (with no other changes) allows me to start the container with the TFTP server booting successfully:
|
Tftp server is running. It's just an issue with the webapp not being able to get the version due to this upstream change: netbootxyz/webapp@f4b77d3 |
Looks like upstream replaced in.tftp with dnsmasq netbootxyz/docker-netbootxyz@fe00be3 |
Is there an existing issue for this?
Current Behavior
When you start the image with the
:latest
tag, the internal TFTP server does not start.Expected Behavior
When you start the image with the
:latest
tag, the internal TFTPserver should start.Steps To Reproduce
Follow the recommended setup guide from TechnoTim
Environment
CPU architecture
arm64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: