'Unable to register with Registry in allotted time' in Geneva development compose file

[jinfahua]

Use docker compose file from here, the virtual device docker cannot be started. Below is log file. It seems that it finally using http://localhost:8500 consul service, which is not available from virtual device service.

level=INFO ts=2020-05-08T08:37:16.869908569Z app=device-virtual source=config.go:219 msg="Loaded configuration from /res/configuration.toml"
level=INFO ts=2020-05-08T08:37:16.870696954Z app=device-virtual source=config.go:167 msg="Using Configuration provider (consul) from: http://edgex-core-consul:8500 with base path of edgex/core/1.0/device-virtual"
level=INFO ts=2020-05-08T08:37:16.876329427Z app=device-virtual source=config.go:321 msg="Configuration has been pulled from Configuration provider (0 environment overrides applied)"
level=ERROR ts=2020-05-08T08:37:16.876364955Z app=device-virtual source=logger.go:74 msg="logTarget cannot be blank, using stdout only"
level=INFO ts=2020-05-08T08:37:16.876390315Z app=device-virtual source=registry.go:79 msg="Using Registry (consul) from http://localhost:8500"
level=INFO ts=2020-05-08T08:37:16.877459523Z app=device-virtual source=config.go:308 msg="Writeable configuration has been updated from the Configuration Provider"
level=WARN ts=2020-05-08T08:37:16.877880295Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:17.878956726Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:18.879985579Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:19.881063027Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:20.882058479Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:21.883053127Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:22.884044029Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:23.885052145Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:24.886126492Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:25.887132598Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:26.888090213Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:27.889085337Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:28.890089518Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:29.891150097Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:30.892154954Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:31.893233021Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:32.894198148Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:33.89522399Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:34.896203372Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:35.897230938Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:36.898300995Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:37.899338436Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:38.900298079Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:39.901284867Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:40.902298227Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:41.903377517Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:42.904374304Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:43.905450905Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:44.90645977Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T08:37:45.907535897Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=ERROR ts=2020-05-08T08:37:46.907662304Z app=device-virtual source=bootstrap.go:43 msg="unable to register with Registry in allotted time"

Below is running docker instances.

$ docker ps
CONTAINER ID        IMAGE                                                                  COMMAND                  CREATED             STATUS              PORTS                                                                                              NAMES
cd8c1f38d4fb        emqx/kuiper:0.3.2                                                      "/usr/bin/docker-ent…"   2 hours ago         Up 2 hours          0.0.0.0:20498->20498/tcp, 9081/tcp, 0.0.0.0:48075->48075/tcp                                       edgex-kuiper
4bc85104930d        nexus3.edgexfoundry.org:10004/docker-edgex-ui-go:master                "./edgex-ui-server -…"   2 hours ago         Up 2 hours          0.0.0.0:4000->4000/tcp                                                                             edgex-ui-go
c2e34ec3e979        nexus3.edgexfoundry.org:10004/docker-core-command-go:master            "/core-command -cp=c…"   2 hours ago         Up 2 hours          0.0.0.0:48082->48082/tcp                                                                           edgex-core-command
f79e6087203d        nexus3.edgexfoundry.org:10004/docker-support-scheduler-go:master       "/support-scheduler …"   2 hours ago         Up 2 hours          0.0.0.0:48085->48085/tcp                                                                           edgex-support-scheduler
a66f07c60ec8        nexus3.edgexfoundry.org:10004/docker-app-service-configurable:master   "/app-service-config…"   2 hours ago         Up 2 hours          48095/tcp, 0.0.0.0:48100->48100/tcp                                                                edgex-app-service-configurable-rules
1f0c90b3d8f7        nexus3.edgexfoundry.org:10004/docker-sys-mgmt-agent-go:master          "/sys-mgmt-agent -cp…"   2 hours ago         Up 2 hours          0.0.0.0:48090->48090/tcp                                                                           edgex-sys-mgmt-agent
3da4d226e1d1        nexus3.edgexfoundry.org:10004/docker-core-data-go:master               "/core-data -cp=cons…"   2 hours ago         Up 2 hours          0.0.0.0:5563->5563/tcp, 0.0.0.0:48080->48080/tcp                                                   edgex-core-data
9d3905035a1c        nexus3.edgexfoundry.org:10004/docker-support-notifications-go:master   "/support-notificati…"   2 hours ago         Up 2 hours          0.0.0.0:48060->48060/tcp                                                                           edgex-support-notifications
d597f769fd43        nexus3.edgexfoundry.org:10004/docker-core-metadata-go:master           "/core-metadata -cp=…"   2 hours ago         Up 2 hours          0.0.0.0:48081->48081/tcp, 48082/tcp                                                                edgex-core-metadata
d0b9c010e951        nexus3.edgexfoundry.org:10004/docker-edgex-mongo:master                "/edgex-mongo/bin/ed…"   2 hours ago         Up 2 hours          0.0.0.0:27017->27017/tcp                                                                           edgex-mongo
b649ec8096c5        nexus3.edgexfoundry.org:10004/docker-edgex-consul:master               "edgex-consul-entryp…"   2 hours ago         Up 2 hours          0.0.0.0:8400->8400/tcp, 8300-8302/tcp, 8301-8302/udp, 8600/tcp, 8600/udp, 0.0.0.0:8500->8500/tcp   edgex-core-consul
e28a4da5e2b0        ubuntu:latest                                                          "tail -f /dev/null"      2 hours ago         Up 2 hours                                                                                                             edgex-files

[cloudxxx8]

you should file this issue in https://github.com/edgexfoundry/device-virtual-go
May I know which docker-compose file you are using?

[cloudxxx8]

please confirm you are using the latest version of developer-script
thanks

[jinfahua]

Yes, it should be the latest version of script, refer to below.

$ ls -l
total 92
-rw-rw-r-- 1 ubuntu ubuntu 17270 May  8 06:31 docker-compose-nexus-mongo-arm64.yml
-rw-rw-r-- 1 ubuntu ubuntu 11040 May  8 06:31 docker-compose-nexus-mongo-no-secty-arm64.yml
-rw-rw-r-- 1 ubuntu ubuntu 10814 May  8 06:31 docker-compose-nexus-mongo-no-secty.yml
-rw-rw-r-- 1 ubuntu ubuntu 17136 May  8 06:31 docker-compose-nexus-mongo.yml
-rw-rw-r-- 1 ubuntu ubuntu 10112 May  8 06:31 docker-compose-nexus-redis-no-secty-arm64.yml
-rw-rw-r-- 1 ubuntu ubuntu  9957 May  8 06:31 docker-compose-nexus-redis-no-secty.yml
-rw-rw-r-- 1 ubuntu ubuntu  1164 May  8 06:31 docker-compose-portainer.yml

[cloudxxx8]

May I know which one you are using?

[jinfahua]

I tried both docker-compose-nexus-redis-no-secty.yml & docker-compose-nexus-mongo-no-secty.yml. The log here is using docker-compose-nexus-mongo-no-secty.yml.

[cloudxxx8]

everything looks good on my VM. Could you please provide the detailed recreate steps?

~/edgex/developer-scripts/releases/nightly-build/compose-files$ docker-compose -f docker-compose-nexus-mongo-no-secty.yml up -d
Creating network "compose-files_edgex-network" with driver "bridge"
Creating volume "compose-files_db-data" with default driver
Creating volume "compose-files_log-data" with default driver
Creating volume "compose-files_consul-config" with default driver
Creating volume "compose-files_consul-data" with default driver
Creating edgex-core-consul ... done
Creating edgex-mongo       ... done
Creating edgex-support-scheduler     ... done
Creating edgex-support-notifications ... done
Creating edgex-core-metadata         ... done
Creating edgex-core-command          ... done
Creating edgex-core-data             ... done
Creating edgex-app-service-configurable-rules ... done
Creating edgex-device-virtual                 ... done
Creating edgex-ui-go                          ... done
Creating edgex-sys-mgmt-agent                 ... done
Creating edgex-kuiper                         ... done
cloud@cloud-Virtual-Machine:~/edgex/developer-scripts/releases/nightly-build/compose-files$ docker logs edgex-device-virtual
level=INFO ts=2020-05-08T10:06:22.30407055Z app=device-virtual source=config.go:219 msg="Loaded configuration from /res/configuration.toml"
level=INFO ts=2020-05-08T10:06:22.304980924Z app=device-virtual source=environment.go:327 msg="Environment override of 'Service.Host' by environment variable: Service_Host=edgex-device-virtual"
level=INFO ts=2020-05-08T10:06:22.305072521Z app=device-virtual source=environment.go:327 msg="Environment override of 'Registry.Host' by environment variable: Registry_Host=edgex-core-consul"
level=INFO ts=2020-05-08T10:06:22.305148019Z app=device-virtual source=environment.go:327 msg="Environment override of 'Clients.Metadata.Host' by environment variable: Clients_Metadata_Host=edgex-core-metadata"
level=INFO ts=2020-05-08T10:06:22.305733502Z app=device-virtual source=config.go:167 msg="Using Configuration provider (consul) from: http://edgex-core-consul:8500 with base path of edgex/core/1.0/device-virtual"
level=INFO ts=2020-05-08T10:06:22.77847169Z app=device-virtual source=config.go:321 msg="Configuration has been pushed to into Configuration Provider (3 environment overrides applied)"
level=ERROR ts=2020-05-08T10:06:22.778661185Z app=device-virtual source=logger.go:74 msg="logTarget cannot be blank, using stdout only"
level=INFO ts=2020-05-08T10:06:22.778806181Z app=device-virtual source=registry.go:79 msg="Using Registry (consul) from http://edgex-core-consul:8500"
level=INFO ts=2020-05-08T10:06:22.780932019Z app=device-virtual source=config.go:308 msg="Writeable configuration has been updated from the Configuration Provider"
level=INFO ts=2020-05-08T10:06:22.801656123Z app=device-virtual source=httpserver.go:89 msg="Web server starting (edgex-device-virtual:49990)"
level=INFO ts=2020-05-08T10:06:22.801877416Z app=device-virtual source=init.go:134 msg="Check Metadata service's status via Registry..."
level=INFO ts=2020-05-08T10:06:22.8024555Z app=device-virtual source=init.go:134 msg="Check Data service's status via Registry..."
level=ERROR ts=2020-05-08T10:06:22.808532425Z app=device-virtual source=init.go:149 msg=" edgex-core-data service not healthy..."
level=ERROR ts=2020-05-08T10:06:22.808770518Z app=device-virtual source=init.go:149 msg=" edgex-core-metadata service not healthy..."
level=INFO ts=2020-05-08T10:06:27.808910102Z app=device-virtual source=init.go:134 msg="Check Metadata service's status via Registry..."
level=INFO ts=2020-05-08T10:06:27.809306791Z app=device-virtual source=init.go:134 msg="Check Data service's status via Registry..."
level=ERROR ts=2020-05-08T10:06:27.816707976Z app=device-virtual source=init.go:149 msg=" edgex-core-metadata service not healthy..."
level=ERROR ts=2020-05-08T10:06:27.817821743Z app=device-virtual source=init.go:149 msg=" edgex-core-data service not healthy..."
level=INFO ts=2020-05-08T10:06:32.817176688Z app=device-virtual source=init.go:134 msg="Check Metadata service's status via Registry..."
level=INFO ts=2020-05-08T10:06:32.819569118Z app=device-virtual source=init.go:134 msg="Check Data service's status via Registry..."
level=INFO ts=2020-05-08T10:06:32.825303049Z app=device-virtual source=init.go:42 msg="Service clients initialize successful."
level=INFO ts=2020-05-08T10:06:32.846086339Z app=device-virtual source=service.go:83 msg="Device Service device-virtual doesn't exist, creating a new one"
level=INFO ts=2020-05-08T10:06:32.851696074Z app=device-virtual source=service.go:140 msg="Addressable device-virtual doesn't exist, creating a new one"
level=INFO ts=2020-05-08T10:06:33.251659809Z app=device-virtual source=device.go:58 msg="Added device: Random-Boolean-Device"
level=INFO ts=2020-05-08T10:06:33.306188204Z app=device-virtual source=device.go:58 msg="Added device: Random-Integer-Device"
level=INFO ts=2020-05-08T10:06:33.332600527Z app=device-virtual source=device.go:58 msg="Added device: Random-Float-Device"
level=INFO ts=2020-05-08T10:06:33.334460772Z app=device-virtual source=device.go:58 msg="Added device: Random-UnsignedInteger-Device"
level=INFO ts=2020-05-08T10:06:33.340416497Z app=device-virtual source=message.go:50 msg="Service dependencies resolved..."
level=INFO ts=2020-05-08T10:06:33.340584792Z app=device-virtual source=message.go:51 msg="Starting device-virtual 1.2.0-dev.12 "
level=INFO ts=2020-05-08T10:06:33.340657289Z app=device-virtual source=message.go:55 msg="device virtual started"
level=INFO ts=2020-05-08T10:06:33.340714188Z app=device-virtual source=message.go:58 msg="Service started in: 11.039257063s"
level=INFO ts=2020-05-08T10:06:33.341788056Z app=device-virtual source=autodiscovery.go:19 msg="AutoDiscovery stopped: disabled by configuration"
level=INFO ts=2020-05-08T10:06:33.354174792Z app=device-virtual source=device.go:58 msg="Added device: Random-Binary-Device"

[jinfahua]

Refer to below steps.

# ubuntu @ ip-172-31-14-191 in ~ [10:21:04]
$ docker stop `docker ps -qa`
cd8c1f38d4fb
3d73fdba8197
4bc85104930d
c2e34ec3e979
f79e6087203d
a66f07c60ec8
1f0c90b3d8f7
3da4d226e1d1
9d3905035a1c
d597f769fd43
cccb0c3a7148
d0b9c010e951
b649ec8096c5
e28a4da5e2b0

# ubuntu @ ip-172-31-14-191 in ~ [10:21:27]
$ docker rm -f $(docker ps -a -q)
cd8c1f38d4fb
3d73fdba8197
4bc85104930d
c2e34ec3e979
f79e6087203d
a66f07c60ec8
1f0c90b3d8f7
3da4d226e1d1
9d3905035a1c
d597f769fd43
cccb0c3a7148
d0b9c010e951
b649ec8096c5
e28a4da5e2b0

# ubuntu @ ip-172-31-14-191 in ~ [10:21:31]
$ docker volume prune
WARNING! This will remove all local volumes not used by at least one container.
Are you sure you want to continue? [y/N] y
Deleted Volumes:
compose-files_db-data
compose-files_consul-config
compose-files_consul-data
compose-files_log-data
cbcdee7b781ad6108fa920389c801f6472c351caf29680786a8cebf863560c8e

Total reclaimed space: 317.2MB

$ docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

# ubuntu @ ip-172-31-14-191 in /tmp/developer-scripts/releases/nightly-build/compose-files on git:master o [10:22:58]
$ ls -l
total 92
-rw-rw-r-- 1 ubuntu ubuntu 17270 May  8 06:31 docker-compose-nexus-mongo-arm64.yml
-rw-rw-r-- 1 ubuntu ubuntu 11040 May  8 06:31 docker-compose-nexus-mongo-no-secty-arm64.yml
-rw-rw-r-- 1 ubuntu ubuntu 10814 May  8 06:31 docker-compose-nexus-mongo-no-secty.yml
-rw-rw-r-- 1 ubuntu ubuntu 17136 May  8 06:31 docker-compose-nexus-mongo.yml
-rw-rw-r-- 1 ubuntu ubuntu 10112 May  8 06:31 docker-compose-nexus-redis-no-secty-arm64.yml
-rw-rw-r-- 1 ubuntu ubuntu  9957 May  8 06:31 docker-compose-nexus-redis-no-secty.yml
-rw-rw-r-- 1 ubuntu ubuntu  1164 May  8 06:31 docker-compose-portainer.yml

# ubuntu @ ip-172-31-14-191 in /tmp/developer-scripts/releases/nightly-build/compose-files on git:master o [10:23:01]
$ git pull
Already up to date.

# ubuntu @ ip-172-31-14-191 in /tmp/developer-scripts/releases/nightly-build/compose-files on git:master o [10:23:08]
$ docker-compose -f ./docker-compose-nexus-mongo-no-secty.yml up -d --build
Creating volume "compose-files_db-data" with default driver
Creating volume "compose-files_log-data" with default driver
Creating volume "compose-files_consul-config" with default driver
Creating volume "compose-files_consul-data" with default driver
Creating edgex-files ... done
Creating edgex-core-consul ... done
Creating edgex-mongo       ... done
Creating edgex-support-logging ... done
Creating edgex-core-data             ... done
Creating edgex-support-notifications          ... done
Creating edgex-sys-mgmt-agent                 ... done
Creating edgex-core-metadata         ... done
Creating edgex-core-command                   ... done
Creating edgex-support-scheduler     ... done
Creating edgex-app-service-configurable-rules ... done
Creating edgex-ui-go                          ... done
Creating edgex-device-virtual                 ... done
Creating edgex-kuiper                         ... done

# ubuntu @ ip-172-31-14-191 in /tmp/developer-scripts/releases/nightly-build/compose-files on git:master o [10:23:56]
$ docker logs edgex-device-virtual
level=INFO ts=2020-05-08T10:23:54.8158712Z app=device-virtual source=config.go:219 msg="Loaded configuration from /res/configuration.toml"
level=INFO ts=2020-05-08T10:23:54.816706415Z app=device-virtual source=config.go:167 msg="Using Configuration provider (consul) from: http://edgex-core-consul:8500 with base path of edgex/core/1.0/device-virtual"
level=INFO ts=2020-05-08T10:23:54.986574809Z app=device-virtual source=config.go:321 msg="Configuration has been pushed to into Configuration Provider (0 environment overrides applied)"
level=ERROR ts=2020-05-08T10:23:54.986610917Z app=device-virtual source=logger.go:74 msg="logTarget cannot be blank, using stdout only"
level=INFO ts=2020-05-08T10:23:54.986628711Z app=device-virtual source=registry.go:79 msg="Using Registry (consul) from http://localhost:8500"
level=INFO ts=2020-05-08T10:23:54.987244429Z app=device-virtual source=config.go:308 msg="Writeable configuration has been updated from the Configuration Provider"
level=WARN ts=2020-05-08T10:23:54.988458632Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:23:55.989499747Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:23:56.990557984Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:23:57.991612933Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:23:58.992606682Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:23:59.993550594Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:00.994540044Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:01.995546703Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:02.996504717Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:03.997545239Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:04.998556454Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:05.999554731Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:07.000514643Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:08.001503455Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:09.002481869Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:10.003524025Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:11.004431545Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:12.005413236Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:13.00640991Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:14.00737881Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:15.008459937Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:16.009430965Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:17.010370309Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:18.011344174Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:19.012296748Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:20.013238322Z app=device-virtual source=registry.go:139 msg="registry is not available"
level=WARN ts=2020-05-08T10:24:21.014196067Z app=device-virtual source=registry.go:139 msg="registry is not available"

$ docker ps -a
CONTAINER ID        IMAGE                                                                  COMMAND                  CREATED              STATUS                      PORTS                                                                                              NAMES
391da2655b7e        emqx/kuiper:0.3.2                                                      "/usr/bin/docker-ent…"   About a minute ago   Up About a minute           0.0.0.0:20498->20498/tcp, 9081/tcp, 0.0.0.0:48075->48075/tcp                                       edgex-kuiper
9c2c5dddcde3        nexus3.edgexfoundry.org:10004/docker-device-virtual-go:master          "/device-virtual --c…"   About a minute ago   Exited (1) 34 seconds ago                                                                                                      edgex-device-virtual
e8264518ccd8        nexus3.edgexfoundry.org:10004/docker-edgex-ui-go:master                "./edgex-ui-server -…"   About a minute ago   Up About a minute           0.0.0.0:4000->4000/tcp                                                                             edgex-ui-go
b440ae9be553        nexus3.edgexfoundry.org:10004/docker-app-service-configurable:master   "/app-service-config…"   About a minute ago   Up About a minute           48095/tcp, 0.0.0.0:48100->48100/tcp                                                                edgex-app-service-configurable-rules
7a1266ffb5aa        nexus3.edgexfoundry.org:10004/docker-support-scheduler-go:master       "/support-scheduler …"   About a minute ago   Up About a minute           0.0.0.0:48085->48085/tcp                                                                           edgex-support-scheduler
a2c34be243f9        nexus3.edgexfoundry.org:10004/docker-core-command-go:master            "/core-command -cp=c…"   About a minute ago   Up About a minute           0.0.0.0:48082->48082/tcp                                                                           edgex-core-command
fef40b6ffbcf        nexus3.edgexfoundry.org:10004/docker-support-notifications-go:master   "/support-notificati…"   About a minute ago   Up About a minute           0.0.0.0:48060->48060/tcp                                                                           edgex-support-notifications
695fc583c4ab        nexus3.edgexfoundry.org:10004/docker-sys-mgmt-agent-go:master          "/sys-mgmt-agent -cp…"   About a minute ago   Up About a minute           0.0.0.0:48090->48090/tcp                                                                           edgex-sys-mgmt-agent
3544312ff2c5        nexus3.edgexfoundry.org:10004/docker-core-metadata-go:master           "/core-metadata -cp=…"   About a minute ago   Up About a minute           0.0.0.0:48081->48081/tcp, 48082/tcp                                                                edgex-core-metadata
5c896405a3c8        nexus3.edgexfoundry.org:10004/docker-core-data-go:master               "/core-data -cp=cons…"   About a minute ago   Up About a minute           0.0.0.0:5563->5563/tcp, 0.0.0.0:48080->48080/tcp                                                   edgex-core-data
ed8f833ffc2a        nexus3.edgexfoundry.org:10004/docker-support-logging-go:master         "/support-logging -c…"   About a minute ago   Exited (0) 42 seconds ago                                                                                                      edgex-support-logging
c8e3ce538816        nexus3.edgexfoundry.org:10004/docker-edgex-mongo:master                "/edgex-mongo/bin/ed…"   About a minute ago   Up About a minute           0.0.0.0:27017->27017/tcp                                                                           edgex-mongo
7efd98a22fa2        nexus3.edgexfoundry.org:10004/docker-edgex-consul:master               "edgex-consul-entryp…"   About a minute ago   Up About a minute           0.0.0.0:8400->8400/tcp, 8300-8302/tcp, 8301-8302/udp, 8600/tcp, 8600/udp, 0.0.0.0:8500->8500/tcp   edgex-core-consul
b398625cf7f7        ubuntu:latest                                                          "tail -f /dev/null"      About a minute ago   Up About a minute                                                                                                              edgex-files

[jinfahua]

Not sure if the Docker images are correct in my env?

$ docker images | grep nexus3
nexus3.edgexfoundry.org:10004/docker-support-scheduler-go       master                8be07cda211f        38 hours ago        13.1MB
nexus3.edgexfoundry.org:10004/docker-sys-mgmt-agent-go          master                f8ae6e4c0a83        38 hours ago        299MB
nexus3.edgexfoundry.org:10004/docker-support-notifications-go   master                0f7032a0b752        38 hours ago        14.7MB
nexus3.edgexfoundry.org:10004/docker-support-logging-go         master                96d954fd567a        38 hours ago        11.8MB
nexus3.edgexfoundry.org:10004/docker-core-command-go            master                0f396b853c08        38 hours ago        13MB
nexus3.edgexfoundry.org:10004/docker-core-metadata-go           master                552f1affe7cc        38 hours ago        14.4MB
nexus3.edgexfoundry.org:10004/docker-core-data-go               master                b9b77933687d        38 hours ago        23.8MB
nexus3.edgexfoundry.org:10004/docker-app-service-configurable   master                2765b607ecd8        6 days ago          29.9MB
nexus3.edgexfoundry.org:10004/docker-device-virtual-go          master                86eb2cebc0c6        9 days ago          20.9MB
nexus3.edgexfoundry.org:10004/docker-edgex-ui-go                master                11e691f785b1        2 weeks ago         21.4MB
nexus3.edgexfoundry.org:10004/docker-edgex-consul               master                9af65397ea6d        2 weeks ago         139MB
nexus3.edgexfoundry.org:10004/docker-edgex-mongo                master                d26c2e80933d        7 weeks ago         403MB

[lenny-goodell]

The issue is the configuration for Registry is using localhost, not the docker network name.

"Using Registry (consul) from http://localhost:8500"

This can occur if you ran naively and didn't clean consul before running in docker. Be sure to "clean" docker before running by doing the following:

• docker-compose -f down
• remove all stopped containers
• prune all volumes

Now try running docker stack.

[jinfahua]

@lenny-intel Yes, I removed all of docker instances, and prune all volumes. It still has the same problem.

[jinfahua]

I tried another VM, it works fine. Not sure what's the problem..

[lenny-goodell]

@lenny-intel Yes, I removed all of docker instances, and prune all volumes. It still has the same problem.

The latest master tagged images are not automatically pulled each time you run, so you may have old images. Try docker-compose -f <file> pull to force pulling all new images.