github-starred/newt
2
0
Fork 0
mirror of https://github.com/fosrl/newt.git synced 2026-03-08 23:03:03 -05:00
Code Issues 21 Packages Projects Releases 25 Wiki Activity

Have newt react to changes in docker #63

New Issue
Closed
opened 2025-11-19 07:13:06 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-19 07:13:06 -06:00
Owner
Copy Link

Originally created by @DennaGherlyn on GitHub (Sep 20, 2025).

Originally assigned to: @oschwartz10612 on GitHub.

Hi, its me again.

so, I noticed another thing. Each time I add a new resource via labels I need to restart Newt, otherwise I only get "Bad Gateway" when accessing the URL. This happens on creating and rebooting a container.

The logs (pangolin, gerbil, newt) does not output any warnings or errors. Newt just prints Blueprint applied successfully!

Steps to reproduce:

  • Add docker-compose container with pangolin labels
  • Start the container
  • Access URL => Bad gateway
  • Restart Newt
  • Access URL => Everything works
  • Reboot container with the labels
  • Access URL => Bad gateway again
Originally created by @DennaGherlyn on GitHub (Sep 20, 2025). Originally assigned to: @oschwartz10612 on GitHub. Hi, its me again. so, I noticed another thing. Each time I add a new resource via labels I need to restart Newt, otherwise I only get "Bad Gateway" when accessing the URL. This happens on creating and rebooting a container. The logs (pangolin, gerbil, newt) does not output any warnings or errors. Newt just prints `Blueprint applied successfully!` **Steps to reproduce:** - Add docker-compose container with pangolin labels - Start the container - Access URL => Bad gateway - Restart Newt - Access URL => Everything works - Reboot container with the labels - Access URL => Bad gateway again
GiteaMirror added the enhancement label 2025-11-19 07:13:06 -06:00
GiteaMirror commented 2025-11-19 07:13:07 -06:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Sep 20, 2025):

Yeah this is because newt only picks up the on the first boot or if
triggered by loading the proxy screen in the dashboard right now. (I
know lol...)

Working on a fix!

@oschwartz10612 commented on GitHub (Sep 20, 2025): Yeah this is because newt only picks up the on the first boot or if triggered by loading the proxy screen in the dashboard right now. (I know lol...) Working on a fix!
GiteaMirror commented 2025-11-19 07:13:07 -06:00
Author
Owner
Copy Link

@DennaGherlyn commented on GitHub (Sep 20, 2025):

So, I know that the resource doesn't show up in the dashboard, only when I trigger the docker discovery it shows up, but even then I need to restart Newt for it to actually work.

Thank you for working on a fix!

@DennaGherlyn commented on GitHub (Sep 20, 2025): So, I know that the resource doesn't show up in the dashboard, only when I trigger the docker discovery it shows up, but even then I need to restart Newt for it to actually work. Thank you for working on a fix!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
good first issue
help wanted
Improvement
pull-request
Mirrored from GitHub Pull Request
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/newt#63
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?