Originally created by @spiralham on GitHub (Jun 5, 2025).
The newt documentation currently states By default, Newt will look for the Docker socket at /var/run/docker.sock, does that mean it has access even without a volume mount in Newt's compose file? I desperately don't want an external resource having a direct line of communication to an internal docker socket, so disabling this Newt-side is a must. Hopefully I'm just misinterpreting the documentation.
Originally created by @spiralham on GitHub (Jun 5, 2025).
The newt documentation currently states `By default, Newt will look for the Docker socket at /var/run/docker.sock`, does that mean it has access even without a volume mount in Newt's compose file? I desperately don't want an external resource having a direct line of communication to an internal docker socket, so disabling this Newt-side is a must. Hopefully I'm just misinterpreting the documentation.
We're going to make it opt-in. In the mean time don't update Newt (you can update Pangolin) if you're not comfortable.
@miloschwartz commented on GitHub (Jun 6, 2025):
We're going to make it opt-in. In the mean time don't update Newt (you can update Pangolin) if you're not comfortable.
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 @spiralham on GitHub (Jun 5, 2025).
The newt documentation currently states
By default, Newt will look for the Docker socket at /var/run/docker.sock, does that mean it has access even without a volume mount in Newt's compose file? I desperately don't want an external resource having a direct line of communication to an internal docker socket, so disabling this Newt-side is a must. Hopefully I'm just misinterpreting the documentation.@miloschwartz commented on GitHub (Jun 6, 2025):
We're going to make it opt-in. In the mean time don't update Newt (you can update Pangolin) if you're not comfortable.
@oschwartz10612 commented on GitHub (Jun 6, 2025):
Fixed in #56
@spiralham commented on GitHub (Jun 6, 2025):
Thank you, appreciate the fast turnaround on this!