kylemanna / kylemanna/docker-openvpn

opvn_getclients second variable not passing through

Open
#613 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
9.1k
Forks
2.4k
PR merge metrics
No merged PRs in 30d

Description

Hi, I am trying to run this one:

docker run -v $OVPN_PKI:/etc/openvpn --rm -it kylemanna/openvpn ovpn_getclient $DEVICE > "/volume2/folder name/$DEVICE.ovpn"

However I keep getting as an output in the folder the message that there are two parameters (three really), combined, combined-save or separate.

This script can produce the client configuration in two formats: 1. combined (default): All needed configuration and cryptographic material is in one file (Use "combined-save" to write the configuration file in the same path as the separated parameter does). 2. separated: Separated files. Please specify one of those options as second parameter.

So I append "combined" to the end of that line:

docker run -v $OVPN_PKI:/etc/openvpn --rm -it kylemanna/openvpn ovpn_getclient $DEVICE > "/volume2/folder name/$DEVICE.ovpn" combined

And I get the same thing happening. I've tried -combined, --combined, -combined-save, you name it. I tried assigning the path to variables and running it that way, but getting the same message, or other odd messages. I've been trying to follow this faq however when I get to generating the OpenVPN client file, that's where it stalls so I can't move further.

Also, second issue, I decided that might be too much trouble and was trying to follow this katacoda scenario for docker-compose, and ran into this error:

bash-4.3# docker-compose run --rm openvpn \
>     ovpn_genconfig -u udp://example.com
Creating network "openvpn_default" with the default driver
Error response from daemon: Bind mount failed: '/volume2/docker/openVPN/openvpn-data/conf' does not exists

Any help would be great. Thanks.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the ovpn_getclient command with its output redirection and the combined argument, then inspect how the command receives positional parameters. Separately, run the shown docker-compose command and investigate the reported bind-mount path; done means both workflows proceed without the displayed parameter or mount errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, shell
Domain
cli, devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.