My newt docker compose file's being ran directly inside my PVE host, which none of my LXC and VMs can see, so I thought using docker compose's labels inside my LXC or VM wouldn't work for me at all, nor did I want to use the newt cli since I didn't want to think about another 3rd party app when things break (I would definitely forget about it).
So I instead added these lines in my newt docker compose file:
to which my blueprint.yaml would have the hostname under targets be the IP of my LXC or VM, and it works fine for my case.
I just thought this would be a good addition, especially to those new to this project, to have this option immediately known to them.
Originally created by @didotb on GitHub (Sep 25, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/151
My newt docker compose file's being ran directly inside my PVE host, which none of my LXC and VMs can see, so I thought using docker compose's labels inside my LXC or VM wouldn't work for me at all, nor did I want to use the newt cli since I didn't want to think about another 3rd party app when things break (I would definitely forget about it).
So I instead added these lines in my newt docker compose file:
```yaml
environment:
- BLUEPRINT_FILE=/blueprint.yaml
volumes:
- /path/to/blueprint.yaml:/blueprint.yaml
```
to which my blueprint.yaml would have the `hostname` under `targets` be the IP of my LXC or VM, and it works fine for my case.
I just thought this would be a good addition, especially to those new to this project, to have this option immediately known to them.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @didotb on GitHub (Sep 25, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/151
My newt docker compose file's being ran directly inside my PVE host, which none of my LXC and VMs can see, so I thought using docker compose's labels inside my LXC or VM wouldn't work for me at all, nor did I want to use the newt cli since I didn't want to think about another 3rd party app when things break (I would definitely forget about it).
So I instead added these lines in my newt docker compose file:
to which my blueprint.yaml would have the
hostnameundertargetsbe the IP of my LXC or VM, and it works fine for my case.I just thought this would be a good addition, especially to those new to this project, to have this option immediately known to them.