A new use case for autodeployment to private network

[empeje]

I currently building my own forticlient docker with a use case that I want to use the docker image as a base image in my gitlab pipeline, then in that pipeline I call some internal API that only accessible via the VPN.

You docker-forticlient works better than mine in connecting to VPN server of forti, however in my use case I run the docker with bash process but I want when I run the bash process, the first thing it should do is connect to vpn. What is the good approach you think? @AuchanDirect

[godric]

👋 @empeje Sorry for the lack of response, are you still interested in an an answer to this question ?

In any case I'm not sure I really understand the question? Specifically:

Use case I run the docker with bash process but I want when I run the bash process, the first thing it should do is connect to vpn