Container restarts

[esturniolo]

Hi!
Thanks for this container.

I follow your guide, but I have two issues:

• The containersrestarts indefinitely
• I can't change the location. It always connects to Tango, Argentina.

This is the docker log:

$ docker logs windscribe 
Starting windscribe ... OK
spawn windscribe login
Windscribe Username: myUserName
Windscribe Password: 
Logged In
Login Successful
spawn windscribe lanbypass on
LAN bybass set to: on
LAN bypass set
spawn windscribe protocol tcp
Default protocol changed to: TCP
Protocol set successfully
spawn windscribe port 80
Default port changed to: 80
Port set successfully
spawn windscribe firewall on
Firewall mode changed to: on
Firewall Enabled
Firewall is on
spawn windscribe connect
Connecting to Argentina Buenos Aires Tango (tcp:80)
Firewall Enabled
/etc/resolv.conf is not a symlink, this may break DNS
Connected to Argentina Buenos Aires Tango
Your IP changed from Unknown to 190.105.226.32
VPN connected
groupadd: group 'docker_group' already exists
useradd: user 'docker_user' already exists
Starting windscribe ... OK
spawn windscribe login
Already Logged in
Loggin Successful
spawn windscribe lanbypass on
LAN bybass set to: on
LAN bypass set
spawn windscribe protocol tcp
Default protocol changed to: TCP
Protocol set successfully
spawn windscribe port 80
Default port changed to: 80
Port set successfully
spawn windscribe firewall on
Firewall mode changed to: on
Firewall Enabled
Firewall is on
spawn windscribe connect
Connecting to Argentina Buenos Aires Tango (tcp:80)
Firewall Enabled
Connected to Argentina Buenos Aires Tango
Your IP changed from yyy.yyy.yyy.yyy to xxx.xxx.xxx.xxx
VPN connected
groupadd: group 'docker_group' already exists
useradd: user 'docker_user' already exists
Starting windscribe ... OK
spawn windscribe login
Already Logged in
Loggin Successful
spawn windscribe lanbypass on
LAN bybass set to: on
LAN bypass set
spawn windscribe protocol tcp
Default protocol changed to: TCP
Protocol set successfully
spawn windscribe port 80
Default port changed to: 80
Port set successfully
spawn windscribe firewall on
Firewall mode changed to: on
Firewall Enabled
Warning, you will not have any internet connectivity if you are not connected to Windscribe
Firewall is on
spawn windscribe connect
Connecting to Argentina Buenos Aires Tango (tcp:80)
Firewall Enabled
Connected to Argentina Buenos Aires Tango
VPN connected
groupadd: group 'docker_group' already exists
useradd: user 'docker_user' already exists
Starting windscribe ... OK
spawn windscribe login
Already Logged in
Loggin Successful
spawn windscribe lanbypass on
LAN bybass set to: on
LAN bypass set
spawn windscribe protocol tcp
Default protocol changed to: TCP
Protocol set successfully
spawn windscribe port 80
Default port changed to: 80
Port set successfully
spawn windscribe firewall on
Firewall mode changed to: on
Firewall Enabled
Firewall is on
spawn windscribe connect
Connecting to Argentina Buenos Aires Tango (tcp:80)
Firewall Enabled
Connected to Argentina Buenos Aires Tango
VPN connected
groupadd: group 'docker_group' already exists
useradd: user 'docker_user' already exists

And this is my docker-compose file:

$ cat docker-compose.yml 
version: "2.1"
services:
  docker-windscribe:
    image: wiorca/docker-windscribe
    container_name: windscribe
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Buenos_Aires
      - WINDSCRIBE_USERNAME=myUserName
      - WINDSCRIBE_PASSWORD=myUltraSecretPassword
      - WINDSCRIBE_PROTOCOL=tcp
      - WINDSCRIBE_PORT=80
      - WINDSCRIBE_PORT_FORWARD=9999
      - WINDSCRIBE_LOCATION=US
      - WINDSCRIBE_LANBYPASS=on
      - WINDSCRIBE_FIREWALL=on
    volumes:
      - /my/own/path/config:/config
    dns:
      - 8.8.8.8
    cap_add:
      - NET_ADMIN
    restart: unless-stopped

Any help is appreciated.
Thanks!!

PD: in the docs you put cap-add in docker-compose, but is cap-add :)

[wiorca]

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.

[wiorca]

Ok, it should be available now. Let me know if these changes fix the issue for you.

[esturniolo]

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.

[wiorca]

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 :)

[esturniolo]

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?

[wiorca]

You can, yes. It's really just a base image I'm using for other things :).