docker: Error response from daemon: Get "https://registry.tld/v2/": dial tcp: lookup registry.tld on 192.168.1.1:53: no such hos

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

docker: Error response from daemon: Get "https://registry.tld/v2/": dial tcp: lookup registry.tld on 192.168.1.1:53: no such hos

L4 Transporter

Hi Guys,

 

What am I missing in my lab? I can see what I have left out or what is a type O.

Any help would be appreciated.

 

[root@conjur1 conjur-setup]# docker images

REPOSITORY     TAG    IMAGE ID    CREATED    SIZE

hello-world    latest   9c7a54a9a43c  4 weeks ago  13.3kB

conjur-appliance  12.7.0.1  05250b532717  9 months ago  1.38GB

[root@conjur1 conjur-setup]# vim /opt/cyberark/conjur/security/seccomp.json

[root@conjur1 conjur-setup]# docker run \

  --name conjur \

  --detach \

  --restart=unless-stopped \

  --security-opt seccomp=/opt/cyberark/conjur/security/seccomp.json \

  --publish "443:443" \

  --publish "444:444" \

  --publish "5432:5432" \

  --publish "1999:1999" \

  --log-driver journald \

  --volume /opt/cyberark/conjur/config:/etc/conjur/config:Z \

  --volume /opt/cyberark/conjur/security:/opt/cyberark/dap/security:Z \

  --volume /opt/cyberark/conjur/backups:/opt/conjur/backup:Z \

  --volume /opt/cyberark/conjur/seeds:/opt/cyberark/dap/seeds:Z \

  --volume /opt/cyberark/conjur/logs:/var/log/conjur:Z \

  registry.tld/conjur-appliance:12.7.0.1

Unable to find image 'registry.tld/conjur-appliance:12.7.0.1' locally

docker: Error response from daemon: Get "https://registry.tld/v2/": dial tcp: lookup registry.tld on 192.168.1.1:53: no such host.

See 'docker run --help'.

1 accepted solution

Accepted Solutions

L7 Applicator

I think in the documentation for Conjur, the term "registry.tld" is a placeholder for the hostname of the container registry server in your organisation, if you are using one. But if you already imported the image locally, you can omit this... meaning you don't specify "registry.tld/" before the image name in the Docker run command.

View solution in original post

2 REPLIES 2

L7 Applicator

I think in the documentation for Conjur, the term "registry.tld" is a placeholder for the hostname of the container registry server in your organisation, if you are using one. But if you already imported the image locally, you can omit this... meaning you don't specify "registry.tld/" before the image name in the Docker run command.

L4 Transporter

Hi Bernard,

 

You are correct it is a placeholder.

 

[root@conjur1 conjur-setup]# docker run   --name conjur   --detach   --restart=unless-stopped   --security-opt seccomp=/opt/cyberark/conjur/security/seccomp.json   --publish "443:443"   --publish "444:444"   --publish "5432:5432"   --publish "1999:1999"   --log-driver journald   --volume /opt/cyberark/conjur/config:/etc/conjur/config:Z   --volume /opt/cyberark/conjur/security:/opt/cyberark/dap/security:Z   --volume /opt/cyberark/conjur/backups:/opt/conjur/backup:Z   --volume /opt/cyberark/conjur/seeds:/opt/cyberark/dap/seeds:Z   --volume /opt/cyberark/conjur/logs:/var/log/conjur:Z   conjur-appliance:12.7.0.1

21d248cf3692ec25bce847dd8b0a6fd8067dd5d98bdcca03572cd0583d67436b

[root@conjur1 conjur-setup]# docker ps

CONTAINER ID  IMAGE            COMMAND         CREATED     STATUS     PORTS                                                                     NAMES

21d248cf3692  conjur-appliance:12.7.0.1  "/bin/keyctl session…"  38 seconds ago  Up 37 seconds  0.0.0.0:443-444->443-444/tcp, :::443-444->443-444/tcp, 0.0.0.0:1999->1999/tcp, :::1999->1999/tcp, 0.0.0.0:5432->5432/tcp, :::5432->5432/tcp  conjur

[root@conjur1 conjur-setup]# 

 

  • 1 accepted solution
  • 361 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!