Kevin Pouget

I confirm the problem and the workaround: ``` data: Corefile: | .:5353 { bufsize 512 errors health { lameduck 20s } ready kubernetes in-addr.arpa ip6.arpa MY_CUSTOM_DOMAIN_HERE { pods insecure fallthrough...

for information, this ^^^ has the negative side effect of breaking the domain name resolution from inside the Pods, which is required for instance by [openshift-acme](https://github.com/tnozicka/openshift-acme) to pre-validate the the...

FYI, here is the way I awaited for the worker Pods to be ready before launching the main container of the Launcher Pod. This avoids running into errors from the...

Hello @carmark, > The `Worker` means worker pod, you can setup it in yaml file. I'm not sure to agree/observe what you're saying:  I request `4`...

The issue is (seems to be at least) that in OpenShift, the pods run with user privileges, so `/etc/hosts...` cannot be modified this way.

FYI, I got the MPI-Operator v0.3.0 running on OpenShift (4.9), here are some notes about how I proceeded (do _not_ assume it's safe, it's only *working*): **Deployment of the operator**...

In addition to what's above, the `Worker` Pod must run with privileges: ``` Worker: replicas: {{ .Nproc }} template: spec: containers: - name: mpi-worker image: {{ .Image }} imagePullPolicy: Always...

pour info j'ai une version de blogotext qui utilise markdown (via pagedown, l'editeur de stackoverflow) > https://github.com/wazari972/blogotext ca marche tres bien chez moi depuis 1 an ou 2; et l'editeur...

related to https://github.com/marian-m12l/studio/issues/262 and https://github.com/marian-m12l/studio/discussions/264

to better understand what script is running, could you tell us which image the driver Pod is running ``` kubectl get pods -n gpu-operator-resources -o=jsonpath='{range .items[*]}{"\n"}{.metadata.name}{":\t"}{range .spec.containers[*]}{.image}{", "}{end}{end}' | grep...