Closed nicolasburtey closed 3 years ago
I'll take a look and see if it breaks anything first as listening on 0.0.0.0 wasn't possible before and a lot of things are using this setup currently.
You can probably use the latest tag though when this is built
I have overridden the command
so I'm good to go. I'll remove the custom command when the next version is released
I spend part of the day trying to integrate specter into a Kubernetes environment. because specter was listening to localhost only by default, specter was not responding to the call from outside the Pod (but it did with
port-forward
which creates some confusion to me) I recommend listening by default to all the network interfaces when it's in the Docker. I think this could save some time for others in the future.