#docker (2022-06)
All things docker
Archive: https://archive.sweetops.com/docker/
2022-06-02
Hey guys,
I have an issue I’m trying to fix now two days straight..
I’m trying to push an image to my private repository which is configured right in the /etc/docker/daemon.json inside insecure-registries.
the daemon.json file looks like this:
{"hosts": ["<tcp://0.0.0.0:2375>", "unix:///var/run/docker.sock"],"insecure-registries" : ["repo-jfrog.shay.com:8081" ]}
when trying to push the image I’m getting the error as follows:
3c9f43f84f93: Pushing [==================================================>] 52.68MB/52.68MB
54ef099e24bc: Pushing 3.072kB
24302eb7d908: Retrying in 1 second
http: server gave HTTP response to HTTPS client
I’ve googled and tried all of the first 10 pages, all of the stackoverflow possible solutions, nothing worked
my docker info is:
Containers: 16
Running: 0
Paused: 0
Stopped: 16
Images: 113
Server Version: 18.09.7
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version:
runc version: N/A
init version: v0.18.0 (expected: fec3683b971d9c3ef73f284f176672c44b448662)
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.4.0-210-generic
Operating System: Ubuntu 16.04.7 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 23.55GiB
Name: prod-vm
ID: 7RPI:OM6S:O2M5:ONBV:QYEW:U47R:LUT2:JVOX:H6PE:SSBA:OUZR:SHE2
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: <https://index.docker.io/v1/>
Labels:
Experimental: false
Insecure Registries:
repo-jfrog.shay.com:8081
127.0.0.0/8
Live Restore Enabled: false
WARNING: API is accessible on <http://0.0.0.0:2375> without encryption.
Access to the remote API is equivalent to root access on the host. Refer
to the 'Docker daemon attack surface' section in the documentation for
more information: <https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface>
WARNING: No swap limit support
my docker service status
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/docker.service.d
└─override.conf
Active: active (running) since Wed 2022-06-01 17:58:27 IST; 1 day 1h ago
Docs: <https://docs.docker.com>
Main PID: 4663 (dockerd)
Tasks: 24
Memory: 85.7M
CPU: 32.621s
CGroup: /system.slice/docker.service
└─4663 /usr/bin/dockerd
Anyone have encountered this before? Any help will be great
maybe a good starting point is to ensure the daemon config is being loaded in the logs via https://docs.docker.com/config/daemon/#read-the-logs
Configuring and troubleshooting the Docker daemon
(it looks like it via the docker into btw)
the daemon.json settings are indeed loaded
@mr.shayv let me know if you have fixed this.. i may be able to help.
@pianoriko2 Couldn’t fix it yet
Tomorrow, we can set a time.. I’m on the east coast..i can walk you through.