Closed esturniolo closed 3 years ago
Re cap-add vs cap_add: Good eye! I missed that, sorry. It will be fixes shortly
Re restarts: I don't really have a process that runs after everything has started up. I suspect running a shell should fix this up.
Re location: Yep, this is a my bad. I forgot to pass it to the connect command. Fix is being pushed now.
Ok, it should be available now. Let me know if these changes fix the issue for you.
Thanks!!! Now connects to different locations.
About the restarts, I can't understand something: This container can't be connected to windscribe in idle mode? My idea is using it as a bridge for other services. Like you do with your other containers, but using one single connection to N services and not one connection to one service. I don't know if I explained properly.
You did, yes. You want to use the container networking feature :).
It's not something I've done personally, but there's no reason why it shouldn't work once the container stays alive. I just set it up as a base for my own convenience :)
You want to use the container networking feature :).
Exactly!
Sorry for my ignorance, but how can I prevent the restart loop of the container? I made some (little) dockerfiles, but I'm a still newbie with docker. Should I add something as entrypoint?
You can, yes. It's really just a base image I'm using for other things :).
Hi! Thanks for this container.
I follow your guide, but I have two issues:
This is the docker log:
And this is my docker-compose file:
Any help is appreciated. Thanks!!
PD: in the docs you put
cap-add
in docker-compose, but iscap-add
:)