dockerize command failing #254

stonegen · 2021-05-21T17:23:37Z

stonegen
May 21, 2021

Hello, I am trying to deploy AdvantEdge but getting the following error when issued command meepctl dockerize all -v:
Get https://meep-docker-registry:30001/v2/: dial tcp 203.135.63.26:30001: connect: connection refused

Error: Failed to push meep-docker-registry:30001/meep-auth-svc with error: exit status 1

Details

mobile@mirinda:~$ meepctl config
Using repo config file: /home/mobile/AdvantEDGE/.meepctl-repocfg.yaml
Using meepctl config file: /home/mobile/.meepctl.yaml
Get/Set meep environment configuration.
Config file location: ~/.meepctl.yaml

Config file is created with default values if it does not already exist.
Values may be changed using the available commands described below.

Usage:
meepctl config [flags]
meepctl config [command]

Available Commands:
gitdir get/set GIT directory path in the meepctl config file
ip get/set node IP address in the meepctl config file
registry get/set docker registry meepctl config file

Flags:
-h, --help help for config

Global Flags:
-t, --time Display timing information
-v, --verbose Display debug information

Use "meepctl config [command] --help" for more information about a command.

========================================
meep.gitdir : /home/mobile/AdvantEDGE
meep.registry : meep-docker-registry:30001
meep.workdir : /home/mobile/.meep
node.ip : 203.135.63.26

mobile@mirinda:~/AdvantEDGE/go-apps/meepctl$ ./install.sh
meepctl
...clean
...vendor
...lint
...build
...install

mobile@mirinda:~/AdvantEDGE/go-apps/meepctl$ meepctl build all --nolint
Using repo config file: /home/mobile/AdvantEDGE/.meepctl-repocfg.yaml
Using meepctl config file: /home/mobile/.meepctl.yaml
-- meep-auth-svc --

checking external dependencies
building meep-auth-svc

-- meep-mon-engine --

checking external dependencies
building meep-mon-engine

-- meep-platform-ctrl --

checking external dependencies
building meep-platform-ctrl

-- meep-virt-engine --

checking external dependencies
building meep-virt-engine

-- meep-webhook --

checking external dependencies
building meep-webhook

-- meep-frontend --

checking external dependencies
checking local dependencies
- meep-sandbox-ctrl-api
- meep-mon-engine-api
- meep-gis-engine-api
- meep-auth-svc-client
- meep-platform-ctrl-api
building meep-frontend

-- meep-platform-swagger-ui --

creating api files

-- meep-sandbox-swagger-ui --

creating api files

-- meep-gis-engine --

checking external dependencies
building meep-gis-engine

-- meep-loc-serv --

checking external dependencies
building meep-loc-serv

-- meep-metrics-engine --

checking external dependencies
building meep-metrics-engine

-- meep-mg-manager --

checking external dependencies
building meep-mg-manager

-- meep-rnis --

checking external dependencies
building meep-rnis

-- meep-sandbox-ctrl --

checking external dependencies
building meep-sandbox-ctrl

-- meep-tc-engine --

checking external dependencies
building meep-tc-engine

-- meep-tc-sidecar --

checking external dependencies
building meep-tc-sidecar

-- meep-wais --

checking external dependencies
building meep-wais

meepctl deploy dep
Using repo config file: /home/mobile/AdvantEDGE/.meepctl-repocfg.yaml
Using meepctl config file: /home/mobile/.meepctl.yaml
Using docker registry: meep-docker-registry:30001
Skipping meep-couchdb: already deployed -- use [-f, --force] flag to force deployment
Skipping meep-docker-registry: already deployed -- use [-f, --force] flag to force deployment
Skipping meep-grafana: already deployed -- use [-f, --force] flag to force deployment
Skipping meep-influxdb: already deployed -- use [-f, --force] flag to force deployment
Skipping meep-ingress: already deployed -- use [-f, --force] flag to force deployment
Skipping meep-kube-state-metrics: already deployed -- use [-f, --force] flag to force deployment
Skipping meep-open-map-tiles: already deployed -- use [-f, --force] flag to force deployment
Skipping meep-postgis: already deployed -- use [-f, --force] flag to force deployment
Skipping meep-prometheus: already deployed -- use [-f, --force] flag to force deployment
Skipping meep-redis: already deployed -- use [-f, --force] flag to force deployment

mobile@mirinda:~/AdvantEDGE/go-apps/meepctl$ meepctl dockerize all -v
Using repo config file: /home/mobile/AdvantEDGE/.meepctl-repocfg.yaml
Using meepctl config file: /home/mobile/.meepctl.yaml
Dockerize called
[arg] targets: [all]
[flag] registry:
[flag] verbose: true
[flag] time: false
Using docker registry: meep-docker-registry:30001
-- meep-auth-svc --

copy docker data
Using: /home/mobile/AdvantEDGE/config/permissions-open.yaml --> /home/mobile/AdvantEDGE/bin/meep-auth-svc/permissions.yaml
Cmd: [rm -r /home/mobile/AdvantEDGE/bin/meep-auth-svc/permissions.yaml]
Result: OK
Cmd: [cp -r /home/mobile/AdvantEDGE/config/permissions-open.yaml /home/mobile/AdvantEDGE/bin/meep-auth-svc/permissions.yaml]
Result: OK
Cmd: [/bin/sh -c find /home/mobile/AdvantEDGE/bin/meep-auth-svc -type f | xargs sha256sum | sort | sha256sum]
Result: 4a390a5591a7bb8a9be20d0e84714f3999f389a01bb13c8b2c60050ddfbb6a30 -
dockerize meep-auth-svc
Cmd: [docker build --no-cache --rm --label MeepVersion=4a390a5591a7bb8a9be20d0e84714f3999f389a01bb13c8b2c60050ddfbb6a30 -t meep-docker-registry:30001/meep-auth-svc /home/mobile/AdvantEDGE/bin/meep-auth-svc]
Result: Sending build context to Docker daemon 16.17MB
Step 1/7 : FROM debian:9.6-slim
---> 3a08df3c763e
Step 2/7 : COPY ./meep-auth-svc /meep-auth-svc
---> 6eecde08a5c7
Step 3/7 : COPY ./permissions.yaml /permissions.yaml
---> 0c484065b15a
Step 4/7 : RUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends ca-certificates
---> Running in 0727a687268b
Get:1 http://security.debian.org/debian-security stretch/updates InRelease [53.0 kB]
Get:2 http://security.debian.org/debian-security stretch/updates/main amd64 Packages [686 kB]
Ign:3 http://deb.debian.org/debian stretch InRelease
Get:4 http://deb.debian.org/debian stretch-updates InRelease [93.6 kB]
Get:5 http://deb.debian.org/debian stretch Release [118 kB]
Get:6 http://deb.debian.org/debian stretch Release.gpg [2410 B]
Get:7 http://deb.debian.org/debian stretch/main amd64 Packages [7080 kB]
Fetched 8032 kB in 4s (1944 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
libssl1.1 openssl
The following NEW packages will be installed:
ca-certificates libssl1.1 openssl
0 upgraded, 3 newly installed, 0 to remove and 19 not upgraded.
Need to get 2276 kB of archives.
After this operation, 5404 kB of additional disk space will be used.
Get:1 http://security.debian.org/debian-security stretch/updates/main amd64 libssl1.1 amd64 1.1.0l-1deb9u3 [1359 kB]
Get:2 http://security.debian.org/debian-security stretch/updates/main amd64 openssl amd64 1.1.0l-1deb9u3 [749 kB]
Get:3 http://security.debian.org/debian-security stretch/updates/main amd64 ca-certificates all 20200601deb9u2 [168 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 2276 kB in 0s (2533 kB/s)
Selecting previously unselected package libssl1.1:amd64.
(Reading database ... 6318 files and directories currently installed.)
Preparing to unpack .../libssl1.1_1.1.0l-1deb9u3_amd64.deb ...
Unpacking libssl1.1:amd64 (1.1.0l-1deb9u3) ...
Selecting previously unselected package openssl.
Preparing to unpack .../openssl_1.1.0l-1deb9u3_amd64.deb ...
Unpacking openssl (1.1.0l-1deb9u3) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../ca-certificates_20200601deb9u2_all.deb ...
Unpacking ca-certificates (20200601deb9u2) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Setting up libssl1.1:amd64 (1.1.0l-1deb9u3) ...
Setting up openssl (1.1.0l-1deb9u3) ...
Setting up ca-certificates (20200601deb9u2) ...
Updating certificates in /etc/ssl/certs...
137 added, 0 removed; done.
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for ca-certificates (20200601~deb9u2) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Removing intermediate container 0727a687268b
---> c457479db987
Step 5/7 : RUN update-ca-certificates
---> Running in 223dffa7cfbd
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Removing intermediate container 223dffa7cfbd
---> 6e6e6e256027
Step 6/7 : ENTRYPOINT ["/meep-auth-svc"]
---> Running in eef48b90c2ec
Removing intermediate container eef48b90c2ec
---> cbf5164ed165
Step 7/7 : LABEL MeepVersion=4a390a5591a7bb8a9be20d0e84714f3999f389a01bb13c8b2c60050ddfbb6a30
---> Running in bed6a3a50e22
Removing intermediate container bed6a3a50e22
---> f75c02b475d1
Successfully built f75c02b475d1
Successfully tagged meep-docker-registry:30001/meep-auth-svc:latest

Cmd: [docker push meep-docker-registry:30001/meep-auth-svc]
Result: The push refers to repository [meep-docker-registry:30001/meep-auth-svc]
Get https://meep-docker-registry:30001/v2/: dial tcp 203.135.63.26:30001: connect: connection refused

meep-auth-svc with error_ exit status 1E

-- meep-mon-engine --

copy docker data
Cmd: [/bin/sh -c find /home/mobile/AdvantEDGE/bin/meep-mon-engine -type f | xargs sha256sum | sort | sha256sum]
Result: f04aab21ab2df8593e76ca5ee3dc1ad42416699ef6a7dcc4c959baf13ff9d4f7 -
dockerize meep-mon-engine
Cmd: [docker build --no-cache --rm --label MeepVersion=f04aab21ab2df8593e76ca5ee3dc1ad42416699ef6a7dcc4c959baf13ff9d4f7 -t meep-docker-registry:30001/meep-mon-engine /home/mobile/AdvantEDGE/bin/meep-mon-engine]
Result: Sending build context to Docker daemon 32.82MB
Step 1/4 : FROM debian:9.6-slim
---> 3a08df3c763e
Step 2/4 : COPY ./meep-mon-engine /meep-mon-engine
---> 9d116f2c995d
Step 3/4 : ENTRYPOINT ["/meep-mon-engine"]
---> Running in 1473429b2c9c
Removing intermediate container 1473429b2c9c
---> 388ad3a15168
Step 4/4 : LABEL MeepVersion=f04aab21ab2df8593e76ca5ee3dc1ad42416699ef6a7dcc4c959baf13ff9d4f7
---> Running in f2a07332f7dd
Removing intermediate container f2a07332f7dd
---> 9adf89e61a11
Successfully built 9adf89e61a11
Successfully tagged meep-docker-registry:30001/meep-mon-engine:latest

Cmd: [docker push meep-docker-registry:30001/meep-mon-engine]
Result: The push refers to repository [meep-docker-registry:30001/meep-mon-engine]
Get https://meep-docker-registry:30001/v2/: dial tcp 203.135.63.26:30001: connect: connection refused

Error: Failed to push meep-docker-registry:30001/meep-mon-engine with error: exit status 1

-- meep-platform-ctrl --

copy docker data
Using: /home/mobile/AdvantEDGE/bin/meep-platform-swagger-ui --> /home/mobile/AdvantEDGE/bin/meep-platform-ctrl/swagger
Cmd: [rm -r /home/mobile/AdvantEDGE/bin/meep-platform-ctrl/swagger]
Result: OK
Cmd: [cp -r /home/mobile/AdvantEDGE/bin/meep-platform-swagger-ui /home/mobile/AdvantEDGE/bin/meep-platform-ctrl/swagger]
Result: OK
Using: /home/mobile/AdvantEDGE/bin/meep-frontend --> /home/mobile/AdvantEDGE/bin/meep-platform-ctrl/frontend
Cmd: [rm -r /home/mobile/AdvantEDGE/bin/meep-platform-ctrl/frontend]
Result: OK
Cmd: [cp -r /home/mobile/AdvantEDGE/bin/meep-frontend /home/mobile/AdvantEDGE/bin/meep-platform-ctrl/frontend]
Result: OK
Cmd: [/bin/sh -c find /home/mobile/AdvantEDGE/bin/meep-platform-ctrl -type f | xargs sha256sum | sort | sha256sum]
Result: ff0a8ff8ec19ff242cdc61fe6ef1c40e7dc38bf499b33af3511c32810ed2c2a1 -
dockerize meep-platform-ctrl
Cmd: [docker build --no-cache --rm --label MeepVersion=ff0a8ff8ec19ff242cdc61fe6ef1c40e7dc38bf499b33af3511c32810ed2c2a1 -t meep-docker-registry:30001/meep-platform-ctrl /home/mobile/AdvantEDGE/bin/meep-platform-ctrl]
Result: Sending build context to Docker daemon 36.34MB
Step 1/6 : FROM debian:9.6-slim
---> 3a08df3c763e
Step 2/6 : COPY ./meep-platform-ctrl /meep-platform-ctrl
---> e84710a41310
Step 3/6 : COPY ./frontend /frontend
---> 60aae82a8fce
Step 4/6 : COPY ./swagger /swagger
---> 86ac65b32eb3
Step 5/6 : ENTRYPOINT ["/meep-platform-ctrl"]
---> Running in bc22458d9bca
Removing intermediate container bc22458d9bca
---> 97401a428823
Step 6/6 : LABEL MeepVersion=ff0a8ff8ec19ff242cdc61fe6ef1c40e7dc38bf499b33af3511c32810ed2c2a1
---> Running in 796ddf7ad69c
Removing intermediate container 796ddf7ad69c
---> a2173658d0e4
Successfully built a2173658d0e4
Successfully tagged meep-docker-registry:30001/meep-platform-ctrl:latest

Cmd: [docker push meep-docker-registry:30001/meep-platform-ctrl]
Result: The push refers to repository [meep-docker-registry:30001/meep-platform-ctrl]
Get https://meep-docker-registry:30001/v2/: dial tcp 203.135.63.26:30001: connect: connection refused

Error: Failed to push meep-docker-registry:30001/meep-platform-ctrl with error: exit status 1

-- meep-virt-engine --

copy docker data
Using: /home/mobile/AdvantEDGE/charts/meep-loc-serv --> /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-loc-serv
Cmd: [rm -r /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-loc-serv]
Result: OK
Cmd: [cp -r /home/mobile/AdvantEDGE/charts/meep-loc-serv /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-loc-serv]
Result: OK
Using: /home/mobile/AdvantEDGE/charts/meep-rnis --> /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-rnis
Cmd: [rm -r /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-rnis]
Result: OK
Cmd: [cp -r /home/mobile/AdvantEDGE/charts/meep-rnis /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-rnis]
Result: OK
Using: /home/mobile/AdvantEDGE/charts/meep-metrics-engine --> /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-metrics-engine
Cmd: [rm -r /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-metrics-engine]
Result: OK
Cmd: [cp -r /home/mobile/AdvantEDGE/charts/meep-metrics-engine /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-metrics-engine]
Result: OK
Using: /home/mobile/AdvantEDGE/charts/meep-wais --> /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-wais
Cmd: [rm -r /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-wais]
Result: OK
Cmd: [cp -r /home/mobile/AdvantEDGE/charts/meep-wais /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-wais]
Result: OK
Using: /home/mobile/AdvantEDGE/charts/meep-tc-engine --> /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-tc-engine
Cmd: [rm -r /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-tc-engine]
Result: OK
Cmd: [cp -r /home/mobile/AdvantEDGE/charts/meep-tc-engine /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-tc-engine]
Result: OK
Using: /home/mobile/AdvantEDGE/charts/meep-gis-engine --> /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-gis-engine
Cmd: [rm -r /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-gis-engine]
Result: OK
Cmd: [cp -r /home/mobile/AdvantEDGE/charts/meep-gis-engine /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-gis-engine]
Result: OK
Using: /home/mobile/AdvantEDGE/charts/meep-virt-chart-templates --> /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-virt-chart-templates
Cmd: [rm -r /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-virt-chart-templates]
Result: OK
Cmd: [cp -r /home/mobile/AdvantEDGE/charts/meep-virt-chart-templates /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-virt-chart-templates]
Result: OK
Using: /home/mobile/AdvantEDGE/charts/meep-sandbox-ctrl --> /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-sandbox-ctrl
Cmd: [rm -r /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-sandbox-ctrl]
Result: OK
Cmd: [cp -r /home/mobile/AdvantEDGE/charts/meep-sandbox-ctrl /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-sandbox-ctrl]
Result: OK
Using: /home/mobile/AdvantEDGE/go-apps/meep-virt-engine/entrypoint.sh --> /home/mobile/AdvantEDGE/bin/meep-virt-engine/entrypoint.sh
Cmd: [rm -r /home/mobile/AdvantEDGE/bin/meep-virt-engine/entrypoint.sh]
Result: OK
Cmd: [cp -r /home/mobile/AdvantEDGE/go-apps/meep-virt-engine/entrypoint.sh /home/mobile/AdvantEDGE/bin/meep-virt-engine/entrypoint.sh]
Result: OK
Using: /home/mobile/AdvantEDGE/charts/meep-mg-manager --> /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-mg-manager
Cmd: [rm -r /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-mg-manager]
Result: OK
Cmd: [cp -r /home/mobile/AdvantEDGE/charts/meep-mg-manager /home/mobile/AdvantEDGE/bin/meep-virt-engine/meep-mg-manager]
Result: OK
Cmd: [/bin/sh -c find /home/mobile/AdvantEDGE/bin/meep-virt-engine -type f | xargs sha256sum | sort | sha256sum]
Result: 96b98eedd777e9fc3836b99ce1e217ec889d73e4d6683c02cdcb869c99ce0f4f -
dockerize meep-virt-engine
Cmd: [docker build --no-cache --rm --label MeepVersion=96b98eedd777e9fc3836b99ce1e217ec889d73e4d6683c02cdcb869c99ce0f4f -t meep-docker-registry:30001/meep-virt-engine /home/mobile/AdvantEDGE/bin/meep-virt-engine]
Result: Sending build context to Docker daemon 7.809MB
Step 1/16 : FROM debian:9.6-slim
---> 3a08df3c763e
Step 2/16 : COPY ./meep-gis-engine /templates/sandbox/meep-gis-engine
---> ad2449a30e06
Step 3/16 : COPY ./meep-loc-serv /templates/sandbox/meep-loc-serv
---> fe787041383a
Step 4/16 : COPY ./meep-metrics-engine /templates/sandbox/meep-metrics-engine
---> 87ef1ecc90ba
Step 5/16 : COPY ./meep-mg-manager /templates/sandbox/meep-mg-manager
---> 2c8e82a78533
Step 6/16 : COPY ./meep-rnis /templates/sandbox/meep-rnis
---> 42d5c4e860ac
Step 7/16 : COPY ./meep-wais /templates/sandbox/meep-wais
---> 7251d9a9feb5
Step 8/16 : COPY ./meep-sandbox-ctrl /templates/sandbox/meep-sandbox-ctrl
---> 18ae1c610deb
Step 9/16 : COPY ./meep-tc-engine /templates/sandbox/meep-tc-engine
---> 1f4dcd61d147
Step 10/16 : COPY ./meep-virt-chart-templates /templates/scenario/meep-virt-chart-templates
---> 7ddcdf208815
Step 11/16 : COPY ./entrypoint.sh /entrypoint.sh
---> 17e5a0348edc
Step 12/16 : COPY ./meep-virt-engine /meep-virt-engine
---> 1043335383c0
Step 13/16 : ENV HELM_VERSION="v3.3.1"
---> Running in 7ced1f4337b0
Removing intermediate container 7ced1f4337b0
---> 83f165954de2
Step 14/16 : RUN mkdir -p /active && apt-get update && apt-get install -y wget && wget -q https://get.helm.sh/helm-${HELM_VERSION}-linux-amd64.tar.gz -O - | tar -xzO linux-amd64/helm > /usr/local/bin/helm && chmod +x /usr/local/bin/helm && chmod +x /entrypoint.sh
---> Running in b433d61a0b77
Get:1 http://security.debian.org/debian-security stretch/updates InRelease [53.0 kB]
Ign:2 http://deb.debian.org/debian stretch InRelease
Get:3 http://deb.debian.org/debian stretch-updates InRelease [93.6 kB]
Get:4 http://security.debian.org/debian-security stretch/updates/main amd64 Packages [686 kB]
Get:5 http://deb.debian.org/debian stretch Release [118 kB]
Get:6 http://deb.debian.org/debian stretch Release.gpg [2410 B]
Get:7 http://deb.debian.org/debian stretch/main amd64 Packages [7080 kB]
Fetched 8032 kB in 3s (2642 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
ca-certificates libffi6 libgmp10 libgnutls30 libhogweed4 libidn11 libidn2-0
libnettle6 libp11-kit0 libpsl5 libssl1.1 libtasn1-6 libunistring0 openssl
publicsuffix
Suggested packages:
gnutls-bin
The following NEW packages will be installed:
ca-certificates libffi6 libgmp10 libgnutls30 libhogweed4 libidn11 libidn2-0
libnettle6 libp11-kit0 libpsl5 libssl1.1 libtasn1-6 libunistring0 openssl
publicsuffix wget
0 upgraded, 16 newly installed, 0 to remove and 19 not upgraded.
Need to get 5341 kB of archives.
After this operation, 14.6 MB of additional disk space will be used.
Get:1 http://security.debian.org/debian-security stretch/updates/main amd64 libssl1.1 amd64 1.1.0l-1deb9u3 [1359 kB]
Get:2 http://deb.debian.org/debian stretch/main amd64 libgmp10 amd64 2:6.1.2+dfsg-1 [253 kB]
Get:3 http://security.debian.org/debian-security stretch/updates/main amd64 libp11-kit0 amd64 0.23.3-2+deb9u1 [112 kB]
Get:4 http://security.debian.org/debian-security stretch/updates/main amd64 openssl amd64 1.1.0l-1deb9u3 [749 kB]
Get:5 http://security.debian.org/debian-security stretch/updates/main amd64 ca-certificates all 20200601deb9u2 [168 kB]
Get:6 http://deb.debian.org/debian stretch/main amd64 libnettle6 amd64 3.3-1+b2 [192 kB]
Get:7 http://deb.debian.org/debian stretch/main amd64 libhogweed4 amd64 3.3-1+b2 [136 kB]
Get:8 http://deb.debian.org/debian stretch/main amd64 libidn11 amd64 1.33-1+deb9u1 [115 kB]
Get:9 http://deb.debian.org/debian stretch/main amd64 libffi6 amd64 3.2.1-6 [20.4 kB]
Get:10 http://deb.debian.org/debian stretch/main amd64 libtasn1-6 amd64 4.10-1.1+deb9u1 [50.6 kB]
Get:11 http://deb.debian.org/debian stretch/main amd64 libgnutls30 amd64 3.5.8-5+deb9u5 [896 kB]
Get:12 http://deb.debian.org/debian stretch/main amd64 libunistring0 amd64 0.9.6+really0.9.3-0.1 [279 kB]
Get:13 http://deb.debian.org/debian stretch/main amd64 libidn2-0 amd64 0.16-1+deb9u1 [60.7 kB]
Get:14 http://deb.debian.org/debian stretch/main amd64 libpsl5 amd64 0.17.0-3 [41.8 kB]
Get:15 http://deb.debian.org/debian stretch/main amd64 wget amd64 1.18-5+deb9u3 [800 kB]
Get:16 http://deb.debian.org/debian stretch/main amd64 publicsuffix all 20190415.1030-0+deb9u1 [108 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 5341 kB in 1s (4126 kB/s)
Selecting previously unselected package libssl1.1:amd64.
(Reading database ... 6318 files and directories currently installed.)
Preparing to unpack .../00-libssl1.1_1.1.0l-1deb9u3_amd64.deb ...
Unpacking libssl1.1:amd64 (1.1.0l-1deb9u3) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../01-libgmp10_2%3a6.1.2+dfsg-1_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.1.2+dfsg-1) ...
Selecting previously unselected package libnettle6:amd64.
Preparing to unpack .../02-libnettle6_3.3-1+b2_amd64.deb ...
Unpacking libnettle6:amd64 (3.3-1+b2) ...
Selecting previously unselected package libhogweed4:amd64.
Preparing to unpack .../03-libhogweed4_3.3-1+b2_amd64.deb ...
Unpacking libhogweed4:amd64 (3.3-1+b2) ...
Selecting previously unselected package libidn11:amd64.
Preparing to unpack .../04-libidn11_1.33-1+deb9u1_amd64.deb ...
Unpacking libidn11:amd64 (1.33-1+deb9u1) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../05-libffi6_3.2.1-6_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-6) ...
Selecting previously unselected package libp11-kit0:amd64.
Preparing to unpack .../06-libp11-kit0_0.23.3-2+deb9u1_amd64.deb ...
Unpacking libp11-kit0:amd64 (0.23.3-2+deb9u1) ...
Selecting previously unselected package libtasn1-6:amd64.
Preparing to unpack .../07-libtasn1-6_4.10-1.1+deb9u1_amd64.deb ...
Unpacking libtasn1-6:amd64 (4.10-1.1+deb9u1) ...
Selecting previously unselected package libgnutls30:amd64.
Preparing to unpack .../08-libgnutls30_3.5.8-5+deb9u5_amd64.deb ...
Unpacking libgnutls30:amd64 (3.5.8-5+deb9u5) ...
Selecting previously unselected package libunistring0:amd64.
Preparing to unpack .../09-libunistring0_0.9.6+really0.9.3-0.1_amd64.deb ...
Unpacking libunistring0:amd64 (0.9.6+really0.9.3-0.1) ...
Selecting previously unselected package libidn2-0:amd64.
Preparing to unpack .../10-libidn2-0_0.16-1+deb9u1_amd64.deb ...
Unpacking libidn2-0:amd64 (0.16-1+deb9u1) ...
Selecting previously unselected package libpsl5:amd64.
Preparing to unpack .../11-libpsl5_0.17.0-3_amd64.deb ...
Unpacking libpsl5:amd64 (0.17.0-3) ...
Selecting previously unselected package wget.
Preparing to unpack .../12-wget_1.18-5+deb9u3_amd64.deb ...
Unpacking wget (1.18-5+deb9u3) ...
Selecting previously unselected package openssl.
Preparing to unpack .../13-openssl_1.1.0l-1deb9u3_amd64.deb ...
Unpacking openssl (1.1.0l-1deb9u3) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../14-ca-certificates_20200601deb9u2_all.deb ...
Unpacking ca-certificates (20200601deb9u2) ...
Selecting previously unselected package publicsuffix.
Preparing to unpack .../15-publicsuffix_20190415.1030-0+deb9u1_all.deb ...
Unpacking publicsuffix (20190415.1030-0+deb9u1) ...
Setting up libnettle6:amd64 (3.3-1+b2) ...
Setting up libtasn1-6:amd64 (4.10-1.1+deb9u1) ...
Setting up libgmp10:amd64 (2:6.1.2+dfsg-1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Setting up publicsuffix (20190415.1030-0+deb9u1) ...
Setting up libunistring0:amd64 (0.9.6+really0.9.3-0.1) ...
Setting up libssl1.1:amd64 (1.1.0l-1deb9u3) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm in @inc (you may need to install the Term::ReadLine module) (@inc contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
debconf: falling back to frontend: Teletype
Setting up openssl (1.1.0l-1deb9u3) ...
Setting up libffi6:amd64 (3.2.1-6) ...
Setting up ca-certificates (20200601deb9u2) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm in @inc (you may need to install the Term::ReadLine module) (@inc contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
debconf: falling back to frontend: Teletype
Updating certificates in /etc/ssl/certs...
137 added, 0 removed; done.
Setting up libidn11:amd64 (1.33-1+deb9u1) ...
Setting up libidn2-0:amd64 (0.16-1+deb9u1) ...
Setting up libpsl5:amd64 (0.17.0-3) ...
Setting up libhogweed4:amd64 (3.3-1+b2) ...
Setting up libp11-kit0:amd64 (0.23.3-2+deb9u1) ...
Setting up libgnutls30:amd64 (3.5.8-5+deb9u5) ...
Setting up wget (1.18-5+deb9u3) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for ca-certificates (20200601~deb9u2) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Removing intermediate container b433d61a0b77
---> 60b7eac1f2bd
Step 15/16 : ENTRYPOINT ["/entrypoint.sh"]
---> Running in acfb77442266
Removing intermediate container acfb77442266
---> e2be2ed20000
Step 16/16 : LABEL MeepVersion=96b98eedd777e9fc3836b99ce1e217ec889d73e4d6683c02cdcb869c99ce0f4f
---> Running in 047f779ac140
Removing intermediate container 047f779ac140
---> e3e48285cede
Successfully built e3e48285cede
Successfully tagged meep-docker-registry:30001/meep-virt-engine:latest

Cmd: [docker push meep-docker-registry:30001/meep-virt-engine]
Result: The push refers to repository [meep-docker-registry:30001/meep-virt-engine]
Get https://meep-docker-registry:30001/v2/: dial tcp 203.135.63.26:30001: connect: connection refused

Error: Failed to push meep-docker-registry:30001/meep-virt-engine with error: exit status 1

-- meep-webhook --

copy docker data
Cmd: [/bin/sh -c find /home/mobile/AdvantEDGE/bin/meep-webhook -type f | xargs sha256sum | sort | sha256sum]
Result: 2aa2486569ff3984246e7d89a076fd7be049453c28fb7ba1d9af4e0148aa86d3 -
dockerize meep-webhook
Cmd: [docker build --no-cache --rm --label MeepVersion=2aa2486569ff3984246e7d89a076fd7be049453c28fb7ba1d9af4e0148aa86d3 -t meep-docker-registry:30001/meep-webhook /home/mobile/AdvantEDGE/bin/meep-webhook]
Result: Sending build context to Docker daemon 16.71MB
Step 1/4 : FROM debian:9.6-slim
---> 3a08df3c763e
Step 2/4 : ADD meep-webhook /meep-webhook
---> 9c5211ad5073
Step 3/4 : ENTRYPOINT /meep-webhook
---> Running in 8c07b3c011bc
Removing intermediate container 8c07b3c011bc
---> 7938db18137c
Step 4/4 : LABEL MeepVersion=2aa2486569ff3984246e7d89a076fd7be049453c28fb7ba1d9af4e0148aa86d3
---> Running in cd08645fc33f
Removing intermediate container cd08645fc33f
---> 848eaf596be9
Successfully built 848eaf596be9
Successfully tagged meep-docker-registry:30001/meep-webhook:latest

Cmd: [docker push meep-docker-registry:30001/meep-webhook]
Result: The push refers to repository [meep-docker-registry:30001/meep-webhook]
Get https://meep-docker-registry:30001/v2/: dial tcp 203.135.63.26:30001: connect: connection refused

Error: Failed to push meep-docker-registry:30001/meep-webhook with error: exit status 1

-- meep-gis-engine --

copy docker data
Cmd: [/bin/sh -c find /home/mobile/AdvantEDGE/bin/meep-gis-engine -type f | xargs sha256sum | sort | sha256sum]
Result: a49b040f4110181f69850194df415b0ef04c0429c78a9bb69b1b0e1618e8466e -
dockerize meep-gis-engine
Cmd: [docker build --no-cache --rm --label MeepVersion=a49b040f4110181f69850194df415b0ef04c0429c78a9bb69b1b0e1618e8466e -t meep-docker-registry:30001/meep-gis-engine /home/mobile/AdvantEDGE/bin/meep-gis-engine]
Result: Sending build context to Docker daemon 14.38MB
Step 1/4 : FROM debian:9.6-slim
---> 3a08df3c763e
Step 2/4 : COPY ./meep-gis-engine /meep-gis-engine
---> 5724fe84a045
Step 3/4 : ENTRYPOINT ["/meep-gis-engine"]
---> Running in 88ae8cdeccc3
Removing intermediate container 88ae8cdeccc3
---> a8b87a5a24a6
Step 4/4 : LABEL MeepVersion=a49b040f4110181f69850194df415b0ef04c0429c78a9bb69b1b0e1618e8466e
---> Running in a2ecb7dc804b
Removing intermediate container a2ecb7dc804b
---> 33a18c7cbe38
Successfully built 33a18c7cbe38
Successfully tagged meep-docker-registry:30001/meep-gis-engine:latest

Cmd: [docker push meep-docker-registry:30001/meep-gis-engine]
Result: The push refers to repository [meep-docker-registry:30001/meep-gis-engine]
Get https://meep-docker-registry:30001/v2/: dial tcp 203.135.63.26:30001: connect: connection refused

Error: Failed to push meep-docker-registry:30001/meep-gis-engine with error: exit status 1

-- meep-loc-serv --

copy docker data
Cmd: [/bin/sh -c find /home/mobile/AdvantEDGE/bin/meep-loc-serv -type f | xargs sha256sum | sort | sha256sum]
Result: 03a868934fad7a00d16defac09efa91b54af146e7a3b6ba521ac6a729ef47e04 -
dockerize meep-loc-serv
Cmd: [docker build --no-cache --rm --label MeepVersion=03a868934fad7a00d16defac09efa91b54af146e7a3b6ba521ac6a729ef47e04 -t meep-docker-registry:30001/meep-loc-serv /home/mobile/AdvantEDGE/bin/meep-loc-serv]
Result: Sending build context to Docker daemon 13.55MB
Step 1/4 : FROM debian:9.6-slim
---> 3a08df3c763e
Step 2/4 : COPY ./meep-loc-serv /meep-loc-serv
---> 043fedce37be
Step 3/4 : ENTRYPOINT ["/meep-loc-serv"]
---> Running in 3685f522c43a
Removing intermediate container 3685f522c43a
---> eca4dfefa083
Step 4/4 : LABEL MeepVersion=03a868934fad7a00d16defac09efa91b54af146e7a3b6ba521ac6a729ef47e04
---> Running in 8ac7e94bf209
Removing intermediate container 8ac7e94bf209
---> 76066c5cab48
Successfully built 76066c5cab48
Successfully tagged meep-docker-registry:30001/meep-loc-serv:latest

Cmd: [docker push meep-docker-registry:30001/meep-loc-serv]
Result: The push refers to repository [meep-docker-registry:30001/meep-loc-serv]
Get https://meep-docker-registry:30001/v2/: dial tcp 203.135.63.26:30001: connect: connection refused

Error: Failed to push meep-docker-registry:30001/meep-loc-serv with error: exit status 1

-- meep-metrics-engine --

copy docker data
Cmd: [/bin/sh -c find /home/mobile/AdvantEDGE/bin/meep-metrics-engine -type f | xargs sha256sum | sort | sha256sum]
Result: 830775c9e25fb780d981b7d954bea2d01d86b54cb6e4ee3a7da7b1306f64b827 -
dockerize meep-metrics-engine
Cmd: [docker build --no-cache --rm --label MeepVersion=830775c9e25fb780d981b7d954bea2d01d86b54cb6e4ee3a7da7b1306f64b827 -t meep-docker-registry:30001/meep-metrics-engine /home/mobile/AdvantEDGE/bin/meep-metrics-engine]
Result: Sending build context to Docker daemon 13.75MB
Step 1/4 : FROM debian:9.6-slim
---> 3a08df3c763e
Step 2/4 : COPY ./meep-metrics-engine /meep-metrics-engine
---> 54a46ee1d839
Step 3/4 : ENTRYPOINT ["/meep-metrics-engine"]
---> Running in d297cb5b87a1
Removing intermediate container d297cb5b87a1
---> 0d3a4055e726
Step 4/4 : LABEL MeepVersion=830775c9e25fb780d981b7d954bea2d01d86b54cb6e4ee3a7da7b1306f64b827
---> Running in d0c1c2de827b
Removing intermediate container d0c1c2de827b
---> 6cc4dc78cfa6
Successfully built 6cc4dc78cfa6
Successfully tagged meep-docker-registry:30001/meep-metrics-engine:latest

Cmd: [docker push meep-docker-registry:30001/meep-metrics-engine]
^C

Please let me know what could be possibly wrong?

Answered by roymx

May 25, 2021

@stonegen,

thanks for providing hardware specifications; I was asking about hardware because we do observe users using limited hardware which causes image pull backoff like the ones you reported.
In your case, hardware is sufficient.

You are having problems running the external dependencies; therefore we must first start by diagnosing why these are not running.

Please provide the following:

Ubuntu version: lsb_release -a
Runtime environment versions: meepctl version all
Kubernetes node details: kubectl describe node
Pod state details: kubectl describe pods

View full answer

volm92 · 2021-05-24T06:21:46Z

volm92
May 24, 2021

Try to do meepctl delete dep then meepctl delete core, then again meepctl deploy dep and WAIT unti all pods are running.
When they are all running meepctl dockerize all then meepctl deploy core (check all pods are running) then go in 203.135.63.26 in your browser.
I hope this will solve, I'm not expert!

1 reply

stonegen May 25, 2021
Author

Thanks for the reply. I tried the steps you mentioned but the problem remains the same.

It seems the dockerize command is failing due to one of the services is crashing after the dependencies deployment step.

roymx · 2021-05-25T14:25:12Z

roymx
May 25, 2021
Maintainer

Hello @stonegen,

meepctl dockerize command creates the docker containers and pushes them in the meep-docker-registry.
Therefore it is important to make sure that it is (1) running and (2) reachable before executing the command.

In your case, meep-docker-registry is pending which is definitely going to fail dockerizing.

What are your system/VM specs (ram, disk, cpu)?

1 reply

stonegen May 25, 2021
Author

Dear @roymx , thank you very much for the response.

We are using PowerEdge R740 system having model name Intel(R) Xeon(R) Gold 5220 CPU @ 2.20GHz, dual-socket, 18 cores per socket, 128 GB RAM, 2TB hard disk. We are using Ubuntu 18.04.5 LTS, directly installed, with no hypervisor.

The system is showing 1.5% average CPU utilization.

Can you please suggest some specific steps to diagnose the issue?

roymx · 2021-05-25T18:12:07Z

roymx
May 25, 2021
Maintainer

@stonegen,

thanks for providing hardware specifications; I was asking about hardware because we do observe users using limited hardware which causes image pull backoff like the ones you reported.
In your case, hardware is sufficient.

You are having problems running the external dependencies; therefore we must first start by diagnosing why these are not running.

Please provide the following:

Ubuntu version: lsb_release -a
Runtime environment versions: meepctl version all
Kubernetes node details: kubectl describe node
Pod state details: kubectl describe pods

15 replies

stonegen May 29, 2021
Author

Dear @dilallkx, I am extremely thankful for your help. I tried all the steps you mentioned, except the last one (turning OFF huge pages in /usr/share/postgresql/postgresql.conf.sample because i couldn't found this file on my system.). However, I was able to disable huge pages on my system. All the steps couldn't resolve the issue.

The good news is that I was able to deploy AdvantEDGE on the same machine but through the root account. Earlier, I was trying through another account with sudo access.

Kindly let me know if you need any log from my system which can be benificial for other users.

Again, thanks a lot.

dilallkx Jun 1, 2021
Maintainer

Hi @stonegen,

Glad to hear you were able to successfully deploy the platform!

We use the standard uid 1000 and sometimes uid 1001 on most of our systems and have never observed the issues you faced. Perhaps it is specific to your user account (1004) or some specific installation step for docker/k8s/kubeadm that may have been run with different permissions... although this does not explain why only postgis was having an issue. It really looked like the huge_pages issue!

Unless you have additional information you think is pertinent to help identify the exact cause, there is no need to provide us with additional information for the moment.

Thanks again and please let us know if the platform meets your needs!
Best regards!

stonegen Jun 1, 2021
Author

Thanks, @dilallkx,
Currently, I am familiarizing myself with this platform. I may need further help as I will use this platform.

It seems the current platform is more suitable for data plane experiments in the MEC enviroment. However, there is a control plane part of the cellular core and I am thinking more realistic experiments can be done with this platform if the cellular core (e.g., OAI) is inserted in this architecture.

Thanks a lot.

stonegen Jun 1, 2021
Author

Hi @dilallkx,
I am planning to deploy my custom application for testing on this platform. Is there any helping material available which I should consult before starting?

dilallkx Jun 1, 2021
Maintainer

Hi @stonegen,

The AdvantEDGE wiki is the main source of information for the platform, we try to maintain & update it as much as possible.
The following page provides Platform Usage details & examples to help you get started:
https://github.com/InterDigitalInc/AdvantEDGE/wiki/usage-workflow

WRT platform experimentation, it is currently focused on emulating mobile edge networks to allow application developers to test various deployment scenarios & network conditions. We continue to add new features with each release according to our roadmap:

We are definitely open to suggestions if you find something is missing or would be useful to add to the platform. All feedback is very much appreciated!

Thanks again!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

dockerize command failing #254

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 3 comments 17 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

dockerize command failing #254

stonegen May 21, 2021

======================================== meep.gitdir : /home/mobile/AdvantEDGE meep.registry : meep-docker-registry:30001 meep.workdir : /home/mobile/.meep node.ip : 203.135.63.26

Replies: 3 comments · 17 replies

volm92 May 24, 2021

stonegen May 25, 2021 Author

roymx May 25, 2021 Maintainer

stonegen May 25, 2021 Author

roymx May 25, 2021 Maintainer

stonegen May 29, 2021 Author

dilallkx Jun 1, 2021 Maintainer

stonegen Jun 1, 2021 Author

stonegen Jun 1, 2021 Author

dilallkx Jun 1, 2021 Maintainer

stonegen
May 21, 2021

========================================
meep.gitdir : /home/mobile/AdvantEDGE
meep.registry : meep-docker-registry:30001
meep.workdir : /home/mobile/.meep
node.ip : 203.135.63.26

Replies: 3 comments 17 replies

volm92
May 24, 2021

stonegen May 25, 2021
Author

roymx
May 25, 2021
Maintainer

stonegen May 25, 2021
Author

roymx
May 25, 2021
Maintainer

stonegen May 29, 2021
Author

dilallkx Jun 1, 2021
Maintainer

stonegen Jun 1, 2021
Author

stonegen Jun 1, 2021
Author

dilallkx Jun 1, 2021
Maintainer