I am using Docker version 1.11.1, build 5604cbe on Mac OS X
On my Mac machine I am trying to do docker push to private docker registry running on remote VM. I am unable to get SSL to work and want to use insecure registry following instructions on https://docs.docker.com/registry/insecure/ How Can I specify DOCKER_OPTS on my Mac so I can push the image to private registry?
In case other people are having the same Get https://docker.myregistry.io:5000/v1/_ping: x509: certificate signed by unknown authority problem, I've posted a simple solution on my blog: it all boils down, as #manojlds has pointed out, to whitelisting the server in the Advanced preferences.
I got the response on docker forums - https://forums.docker.com/t/where-do-i-set-docker-opts-for-insecure-registry/14542
pinata set daemon '{"storage-driver":"aufs","debug":true,"insecure-registries":["your.insecure.registry.com:5000"]}'
Pinata has been removed from more recent versions. You can setup insecure registries from Preferences -> Advanced.
Currently there is no official CLI based way to do the update.
Related
I can only reproduce this error on my Mac Air. I have a Mac tower from 2010 that I've opencore'd to 12+ and it does not have this issue.
For the life of me, I cannot get through this error with the #matterlabs/hardhat-zksync-solc plugin. As you can see in the window behind my CLI, I am connected to docker hub through Docker Desktop. I can also log into docker via the CLI using docker login. I've already tried logging in and out using various methods.
My last suspicion is that maybe a port is natively blocked? Where would I begin trying to troubleshoot this?
Just answering this to mention that support for Docker has been deprecated and it's recommended that users use binary as compiler source to compile contracts with zksolc.
You can find more info on how to compile contracts on zkSync here: https://v2-docs.zksync.io/dev/developer-guides/contracts/contracts.html
And specific information about the zksolc harhdat plugin here: https://v2-docs.zksync.io/api/hardhat/plugins.html#hardhat-zksync-solc
Anyone know where to look within the various Docker diagnostics files to diagnose why TLS is not working to protect the Docker Daemon on Docker Desktop for Windows?
Tried the following article from Docker and countless other articles to try to protect the Docker Engine using a self-signed TLS cert on Windows, but none have worked.
Use TLS HTTPS to Protect the Docker Daemon Socket
https://docs.docker.com/engine/security/protect-access/#use-tls-https-to-protect-the-docker-daemon-socket
Docker Desktop for Windows versions tried: 2.3.0.4, 3.2.0
OS: Windows 10
The general log file that is produced doesn’t provide a clear answer to the root cause of the issue. Are there certain files within the diagnostic files, which are generated, that might provide better insight as to why TLS is not working?
Thanks!
I recently migrated my dev environment from Windows Home to Pro and as part of the upgrade installed Docker Desktop instead of using Docker Toolbox.
After the upgrade, using the default Docker Desktop instance I kept receiving some variation on the below error.
Error response from daemon: Get https://docker.abc.xyz.net/v1/users/:
x509: certificate is valid for *.xyz.net, xyg.net, not
docker.abc.xyz.net
What could be causing the problem? I have searched around the internet for hours and all the different solutions have no effect. Restarting Docker, uninstall and reinstall.
Can anybody help?
It appears as part of the migration from Docker Toolbox to Docker Desktop a number of entries are leftover in the hosts file on Windows that cause a conflict when Docker is trying to access any external network. The simple fix? Remove these 5 lines from my hosts file
52.3.153.154 index.docker.io
34.200.28.105 registry.docker.io
52.20.146.203 registry-1.docker.io
54.152.209.167 auth.docker.io
52.222.149.24 dseasb33srnrn.cloudfront.net
We are using Windows OS 7 to develop an application using tech stack viz. docker, spring, java8, gradle etc. We have installed the docker toolbox on our machine.
Now the base image is located in our docker repository of our organization. But the docker is not able to identify the host.
We are able to connect to our repository from docker installed on a linux machine. In that case we have made changes in these 2 files viz.
1.
/etc/systemd/system/docker.service.d/daemon.conf
here we have added http_proxy and https_proxy.
2.
/etc/docker/daemon.json
here we have mentioned the host name as
{"insecure-registries":["<host-name>"]}
But we are not able to find these files in docker tool-box in windows 7.
Please let us know how to resolve this issue.
We are getting the following error in dockerBuildImage gradle task currently wherein it is not able to download the base image.
:dockerBuildImage FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':dockerBuildImage'.
> Could not build image: Get https:<host-name>/v2/: x509: certificate signed by unknown authority
Please advise.
The following worked for me in docker toolbox
change the file /var/lib/boot2docker/profile to include following text:
--insecure-registry=<host1-name>
export "NO_PROXY=<host-name>"
export HTTP_PROXY=<value>
export HTTPS_PROXY=<value>
Then restart the docker-machine to make these changes visible.
I took an older macbook back in use. It previously had boot2docker installed when the native docker for mac didn't exist yet. That might be the root cause of my issue.
I've installed the new docker for mac but when I run docker-compose I've got the following error:
docker.errors.TLSParameterError: Path to a certificate and key files must be provided through the client_config param. TLS configurations should map the Docker CLI client configurations. See https://docs.docker.com/engine/articles/https/ for API details.
I don't want to install a docker machine with virtual box or anything. I just want to run it natively like a fresh docker for mac installation. All the solutions I've found so far require me to use a docker-machine.
Fixed it by unsetting all legacy docker machine environment variables so that it uses the correct docker commands
unset ${!DOCKER_*}
I've found the solution on the docker troubleshooting page over here.