Hi, I am following the steps necessary to get Mender working with client certificates and mutual TLS in this link https://docs.mender.io/server-integration/client-certificates, but I am running into issues on the step that requires you to start the edge proxy.:
docker run
-p 443:8080
-e MTLS_MENDER_USER=mtls@mender.io
-e MTLS_MENDER_PASS=password
-e MTLS_MENDER_BACKEND=https://hosted.mender.io
-e MTLS_DEBUG_LOG=true
-v $(pwd)/server-cert.pem:/etc/mtls/certs/server/server.crt
-v $(pwd)/server-private.key:/etc/mtls/certs/server/server.key
-v $(pwd)/ca-cert.pem:/etc/mtls/certs/tenant-ca/tenant.ca.pem
registry.mender.io/mendersoftware/mtls-ambassador:master
I replace the MTLS_MENDER_USER with my username for my free trial of Mender Enterprise, MTLS_MENDER_PASS with my password for my free trial of Mender Enterprise, and MTLS_MENDER_BACKEND with https://hosted.mender.io/ui/#/login since this is where I would log in to access my free Mender Enterprise account. The following volume tags are all left alone and point to the correct locations for the certificates on my system.
When I run the above docker command with the changed fields I get this error:
Unable to find image ‘registry.mender.io/mendersoftware/mtls-ambassador:master’ locally
docker: Error response from daemon: Get https://registry.mender.io/v2/mendersoftware/mtls-ambassador/manifests/master: no basic auth credentials.
See ‘docker run --help’.
As far as I can tell the issue might be a couple of things:
- I should somehow have this docker image already on my local system.
- The registry that currently stores the mender mtls-ambassador/manisfests:master image is currently down.
- My login credentials are incorrect and aren’t what are necessary to access this docker image.
- My server “commonName” field in the server-cert.conf file is incorrect. (It’s currently the default value of “server.com” that was present in the instructions. I wasn’t sure if I needed to change this since the instructions weren’t abundantly clear to me.
Any help is appreciated.
Thanks