0

I have installed anchore-engine using docker-compose in RHEL. Then, I tried to add a docker image for scanning purpose but I'm getting the following error.

[xxx@xxx aevolume]$ docker-compose exec engine-api anchore-cli system wait
Starting checks to wait for anchore-engine to be available timeout=-1.0 interval=5.0
API availability: Checking anchore-engine URL (http://localhost:8228)...
API availability: Success.
Service availability: Checking for service set (catalog,apiext,policy_engine,simplequeue,analyzer)...
Service availability: Success.
Feed sync: Checking sync completion for feed set (vulnerabilities)...
Feed sync: Success.

[xxx@xxx aevolume]$ docker-compose exec engine-api anchore-cli image add docker.io/library/debian:7
Error: cannot fetch image digest/manifest from registry
HTTP Code: 400
Detail: {'error_codes': ['SKOPEO_UNKNOWN_ERROR'], 'raw_exception_message': 'Error encountered in skopeo operation. cmd=/bin/sh -c skopeo   inspect --raw --tls-verify=false  docker://docker.io/library/debian:7, rc=1, stdout=None, stderr=b\'time="2020-04-15T05:19:42Z" level=fatal msg="Error parsing image name \\\\"docker://docker.io/library/debian:7\\\\": error pinging docker registry registry-1.docker.io: Get http://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 127.0.0.11:53: read udp 127.0.0.1:55548->127.0.0.11:53: i/o timeout"\\n\', error_code=SKOPEO_UNKNOWN_ERROR'}

It seems like a proxy issue. So, I've created a file ~/.docker/config.json in docker client that too didn't work.

I've followed this doc for anchore-engine installation.

Navin prasad
  • 558
  • 1
  • 8
  • 18
  • If you believe it is a proxy issue, did your read [this page](https://docs.anchore.com/current/docs/engine/engine_installation/configuration/network_proxies/) in first place ? – Zeitounator Apr 15 '20 at 05:45
  • 1
    Hi @Zeitounator, After reading that page only, I tried with the proxy config. – Navin prasad Apr 15 '20 at 05:51
  • Did you destroy and recreate your containers after setting the proxy in `]~/.docker/config.json` ? The operation fails on trying to resolve dns for docker.io, so it is not using proxy at all at this stage. – Zeitounator Apr 15 '20 at 06:40
  • 1
    Now, I recreated the container. While I am listing the active services using docker compose ps, it's showing the container status as Up (Unhealthy). I've checked the logs of anchore-analyzer, it is showing proxy error. – Navin prasad Apr 15 '20 at 10:50

0 Answers0