skupjoe

EN has settings/context box descriptions in English- CN is full Chinese.

Same issue! ` ovpn_env.sh` is completely missing! How do I use this container?

Hi @dayjaby - Thanks. I tried this (I was previously on 2.4), but I still experienced the same issue. Ultimately, I needed to create an empty `ovpn_env.sh` file and mount...

I think the error is due to using bind mounts on the `/etc/openvpn` directory. If you do this, then this will replace any built-in volumes on that directory which the...

_Side note_ I also found that I needed to set the following to get the container to boot, likely because some env's aren't being set via the missing `ovpn_env.sh` :...

> > Hi @dayjaby - > > Thanks. I tried this (I was previously on 2.4), but I still experienced the same issue. > > Ultimately, I needed to create...

Thanks, @fariszr ! Yes, @git-the-bits- very keen on seeing this image use the latest OpenVPN packages. @kylemanna shouldn't there be automated builds happening?

I am curious about this also. Is there any way to consume these metrics on the other end and provide a Prometheus endpoint that can be scraped?

My resultant auto-generated m3coordinator config from this is the following: ``` kind: ConfigMap apiVersion: v1 metadata: name: m3db-config-map-m3db-cluster namespace: monitoring uid: 8beea769-2b68-488a-a3c3-606622013bcd resourceVersion: '163096500' creationTimestamp: '2021-09-22T23:45:20Z' ownerReferences: - apiVersion: operator.m3db.io/v1alpha1...

I believe that this issue relates to [this](https://github.com/m3db/m3db-operator/commit/a2c1ab82ea0264a6eaf8e8850f67cd42b2c071ef) change. To fix the issue: 1. I provide my own m3coordinator conf by adding this line to my M3DBCluster (operator) config: ```...