Service never starts

[VAggrippino]

I'm attempting to start a dockerflow/docker-flow-proxy service on a swarm with one manager and two workers, but the command never completes and never reports any errors. So, it never returns to the command prompt. Instead, it repeatedly switches between, "new", "assigned", "ready", and "starting".

Note that although the screenshot shows the image vfarcic/docker-flow-proxy I'm having exactly the same problem with dockerflow/docker-flow-proxy.

This is from the book "The DevOps 2.1 Toolkit - Docker Swarm" by @vfarcic
Here's the command I used to start the service

docker service create --name proxy -p 80:80 -p 443:443 -p 8080:8080 --network proxy -e MODE=swarm dockerflow/docker-flow-proxy

If I Ctrl-C it shows

Operation continuing in background.
Use docker service ps p473obsbo9tgjom1fd61or5ap to check progress.

... and returns to the command prompt

If I use docker service ps --no-trunc p473obsbo9tgjom1fd61or5ap I get:

ID                          NAME                IMAGE                                                                                                         NODE                DESIRED STATE       CURRENT STATE               ERROR                                                          PORTS
dbzvr67uzg5fq9w64uh324dtn   proxy.1             dockerflow/docker-flow-proxy:latest@sha256:e4e4a684d703bec18385caed3b3bd0482cefdff73739ae21bd324f5422e17d93   node-1              Running             Starting 11 seconds ago
vzlttk2xdd4ynmr4lir4t38d5    \_ proxy.1         dockerflow/docker-flow-proxy:latest@sha256:e4e4a684d703bec18385caed3b3bd0482cefdff73739ae21bd324f5422e17d93   node-1              Shutdown            Failed 16 seconds ago       "task: non-zero exit (137): dockerexec: unhealthy container"
q5dlvb7xz04cwxv9hpr9w5f7l    \_ proxy.1         dockerflow/docker-flow-proxy:latest@sha256:e4e4a684d703bec18385caed3b3bd0482cefdff73739ae21bd324f5422e17d93   node-1              Shutdown            Failed 49 seconds ago       "task: non-zero exit (137): dockerexec: unhealthy container"
z86h0pcj21joryb3sj59mx2pq    \_ proxy.1         dockerflow/docker-flow-proxy:latest@sha256:e4e4a684d703bec18385caed3b3bd0482cefdff73739ae21bd324f5422e17d93   node-1              Shutdown            Failed about a minute ago   "task: non-zero exit (137): dockerexec: unhealthy container"
uj2axgfm1xxpdxrkp308m28ys    \_ proxy.1         dockerflow/docker-flow-proxy:latest@sha256:e4e4a684d703bec18385caed3b3bd0482cefdff73739ae21bd324f5422e17d93   node-1              Shutdown            Failed about a minute ago   "task: non-zero exit (137): dockerexec: unhealthy container"

So, no mention of node-2 or node-3 and I don't know what the error message means.

If I run docker service logs -f proxy the following repeats every minute or so:

proxy.1.s585dio0clan@node-1    | 2018/09/12 03:13:02 Starting HAProxy
proxy.1.s585dio0clan@node-1    | 2018/09/12 03:13:02 Getting certs from http://202.71.99.195:8080/v1/docker-flow-proxy/certs

I can only guess that it fails to get whatever certs it's looking for. There doesn't seem to be anything at that address, but an IP address lookup shows that it leads to my ISP. Where's that coming from?

Steps to reproduce the issue:

1. Create three nodes with docker-machine
2. Initialize the swarm with the first node as the manager
3. Join the swarm with the other two nodes.
4. Create a network using the overlay driver.
5. Create a service, using dockerflow/docker-flow-proxy; publishing mirrored ports 80, 443, and 8080; and setting the MODE=swarm environment variable.

Describe the results you received:

overall progress: 0 out of 1 tasks
1/1 starting

(never returns to command prompt)

Describe the results you expected:
Something like:

overall progress: 1 out of 1 tasks
verify: Service converged

Additional information you deem important (e.g. issue happens only occasionally):

Additional environment details (AWS, VirtualBox, physical, etc.):
I'm running this on a physical computer running Linux Mint 19 (based on Ubuntu 18.04). The driver / provider for docker-machine is virtualbox.

[thomasjpfan]

@VAggrippino The IP the shows up in Getting certs should be an internal IP supplied by the proxy overlay network. This suggests a networking issue.

1. I recall healthcheck issues running on older version of docker (using virtualbox). What version of docker is your virtualbox using? You can check by running docker version.
2. Can you post the exact commands you used to reproduce your issue?

[thomasjpfan]

docker service create waits for the service to become healthy before continuing. The proxy service is restarting over and over again because it is failing the healthcheck. To check the healthcheck error:

1. docker service ps proxy to get the node your proxy is running on.
2. eval $(docker-machine env INSERT-NODE-HERE) to log into the node
3. docker container ls to get the container ID of the proxy container
4. docker container inspect INSERT-CONTAINER-ID -f '{{ (index .State.Health.Log 0).Output }}' to get the healthcheck outupt.

I suspect its a issue with not being able to ping localhost. Can you post the output of step 4 here?

[VAggrippino]

@thomasjpfan It makes a lot more sense that it should only make requests for certs or anything else from resources on the overlay network. How would I check for any networking issues?

I'm using Docker version 18.06:

vaggrippino@Envy-LM19-64:~/Dev/go-demo$ docker version
Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a
 Built:             Tue Aug 21 17:24:51 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a
  Built:            Tue Aug 21 17:23:15 2018
  OS/Arch:          linux/amd64
  Experimental:     false

Here's the output of docker service ps proxy:

vaggrippino@Envy-LM19-64:~/Dev/go-demo$ docker service ps proxy
ID                  NAME                IMAGE                                 NODE                DESIRED STATE       CURRENT STATE               ERROR                              PORTS
r2d0yrkkj3nf        proxy.1             dockerflow/docker-flow-proxy:latest   node-1              Running             Starting 2 seconds ago
csh80tyblds7         \_ proxy.1         dockerflow/docker-flow-proxy:latest   node-1              Shutdown            Failed 7 seconds ago        "task: non-zero exit (137): do…"
s3r4c36jrkn1         \_ proxy.1         dockerflow/docker-flow-proxy:latest   node-2              Shutdown            Failed 40 seconds ago       "task: non-zero exit (137): do…"
z9rxsj0dcr1m         \_ proxy.1         dockerflow/docker-flow-proxy:latest   node-2              Shutdown            Failed about a minute ago   "task: non-zero exit (137): do…"
tmwmu92rdgen         \_ proxy.1         dockerflow/docker-flow-proxy:latest   node-3              Shutdown            Failed about a minute ago   "task: non-zero exit (137): do…"

... Isn't that the same as when I run it using the service ID that was provided? The output changes each time I run it. One node says "Running" while the others say "Shutdown". The next I run docker service ps, the one that said "Running" will be in the list of those that say "Shutdown".

docker container ls lists one container and indicates that its status is "unhealthy":

vaggrippino@Envy-LM19-64:~/Dev/go-demo$ docker container ls
CONTAINER ID        IMAGE                                 COMMAND                  CREATED             STATUS                      PORTS                       NAMES
e6dfea733688        dockerflow/docker-flow-proxy:latest   "/sbin/tini -g -- do…"   21 seconds ago      Up 15 seconds (unhealthy)   80/tcp, 443/tcp, 8080/tcp   proxy.1.eb3c7fhoqyxnu0e7y9bpn47r7

Running docker container inspect shows "No such container". I think that's consistent with the constantly changing output of docker service ps that I got earlier:

vaggrippino@Envy-LM19-64:~/Dev/go-demo$ docker container inspect e6dfea733688 -f '{{ (index .state.Health.Log 0).Output }}'

Error: No such container: e6dfea733688

Here are all the commands I used leading up to my attempt to start the service. They're all from chapter 3 of the book I mentioned...

Create the nodes:

for i in 1 2 3; do   docker-machine create -d virtualbox node-$i; done

Initialize the swarm using the first node as the manager:

eval $(docker-machine env node-1)
docker swarm init --advertise-addr $(docker-machine ip node-1)

Join the other two nodes to the swarm as workers using the join token generated when the swarm was initialized:

TOKEN=$(docker swarm join-token -q worker)
for i in 2 3; do   eval $(docker-machine env node-$i);   docker swarm join --token $TOKEN --advertise-addr $(docker-machine ip node-$i) $(docker-machine ip node-1):2377; done

Create the proxy overlay network:

eval $(docker-machine env node-1)
docker network create --driver overlay proxy

(Try to) Create the proxy service:
docker service create --name proxy -p 80:80 -p 443:443 -p 8080:8080 --network proxy -e MODE=swarm dockerflow/docker-flow-proxy

[thomasjpfan]

Getting to the healthcheck would help with figuring out what your issue is. Maybe this may help get to it:

1. docker container run --name test_proxy -p 80:80 -p 443:443 -p 8080:8080 -d --rm dockerflow/docker-flow-proxy
2. docker container ls to get the id.
3. Run docker container ls to check if its healthy. If its not healthy, go to step 4.
4. docker container inspect INSERT-CONTAINER-ID -f '{{ (index .State.Health.Log 0).Output }}'

I am not able to reproduce this issue. Are you running the latest version of virtualbox?

[VAggrippino]

It won't even start...

vaggrippino@Envy-LM19-64:~/Dev/go-demo$ docker container run --name test_proxy -p 80:80 -p 443:443 -p 8080:8080 -d --rm dockerflow/docker-flow-proxy
could not read CA certificate "/home/vaggrippino/.docker/machine/machines/node-1/ca.pem": open /home/vaggrippino/.docker/machine/machines/node-1/ca.pem: no such file or directory

It's looking for a security certificate again.

Is this related to the previous error message, or is it just a coincidence?

I know port 443 is typically used for SSL, but at this stage it's just a port number, isn't it? I don't think I've set up anything related to SSL security.

And now, even running docker container ls shows the same could not read CA certificate error message.

[VAggrippino]

Attempt number 2:
I closed my terminal session, getting rid of any changed environment settings, and tried again...

vaggrippino@Envy-LM19-64:~$ docker container run --name test_proxy -p 80:80 -p 443:443 -p 8080:8080 -d --rm dockerflow/docker-flow-proxy
Unable to find image 'dockerflow/docker-flow-proxy:latest' locally
latest: Pulling from dockerflow/docker-flow-proxy
8e3ba11ec2a2: Already exists
88781fb13b71: Pull complete
607bf44a09ca: Pull complete
b72d0d9d6b1c: Pull complete
c3a7ba0a42fa: Pull complete
ea85ff966af3: Pull complete
3605032cc9b2: Pull complete
096e41957612: Pull complete
a2a60320ff8f: Pull complete
1b7df0119465: Pull complete
Digest: sha256:e4e4a684d703bec18385caed3b3bd0482cefdff73739ae21bd324f5422e17d93
Status: Downloaded newer image for dockerflow/docker-flow-proxy:latest
50ef4e502b0725cb4eca19607cef946f5d0257ab05bacbb88b6954a4925d315e

That's consistent with what I've come to expect.
...

vaggrippino@Envy-LM19-64:~$ docker container ls
CONTAINER ID        IMAGE                          COMMAND                  CREATED             STATUS                   PORTS                                                              NAMES
50ef4e502b07        dockerflow/docker-flow-proxy   "/sbin/tini -g -- do…"   7 seconds ago       Up 5 seconds (healthy)   0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:8080->8080/tcp   test_proxy
cb3829ae289f        registry:2.5.0                 "/entrypoint.sh /etc…"   29 hours ago        Up 9 hours               0.0.0.0:5000->5000/tcp                                             registry

I'm not surprised that it's healthy. I forgot to mention that I had started and stopped other containers other docker-machine nodes, and other services without any problem. I didn't start having problems until I tried to create this service with this specific configuration. I thought it must be a problem with docker-flow-proxy, but the test_proxy you just had me create shows that that's not the case. It must be something else.

That registry container is unexpected. It's left over from chapter 1 of this book and it's been there through several reboots. It's probably not related to this issue, though.

[thomasjpfan]

In general, its better to run docker-machine rm at the end of each chapter, to make sure there aren't any conflicts.

could not read CA certificate "/home/vaggrippino/.docker/machine/machines/node-1/ca.pem": open /home/vaggrippino/.docker/machine/machines/node-1/ca.pem: no such file or directory

This issue is unrelated with docker-flow-proxy. It is an issue with the docker command itself. When you run docker-machine it creates certs for you so you can securely connect to the docker API (typically using port 2375). In that case, the certs are not there.

If the docker container run is passes the healthcheck, but docker service create does not pass, it would be a pretty strange issue. You can test if the service runs without the healthcheck:

docker service create --name proxy_nocheck -p 80:80 -p 443:443 -p 8080:8080 --network proxy -e MODE=swarm --health-cmd ""  dockerflow/docker-flow-proxy

You can also try running it without the overlay proxy

docker service create --name proxy_nooverlay -p 80:80 -p 443:443 -p 8080:8080 -e MODE=swarm dockerflow/docker-flow-proxy

The above two commands are just trying to pinpoint the issue.

[thomasjpfan]

I am able to reproduce a similar issue. I'll update this thread when I figure out whats wrong.

Edit: Nevermind, it is not the same issue.

Another test you can do is to create one manager, and run:

docker-machine create -d virtualbox node-1
eval $(docker-machine env node-1)
docker swarm init --advertise-addr $(docker-machine ip node-1)  
docker service create --name proxy -p 80:80 -p 443:443 -p 8080:8080 -e MODE=swarm dockerflow/docker-flow-proxy

[VAggrippino]

Creating the service without the healthcheck results in exactly the same problem, so I guess it's not the healthcheck that's stopping it...

vaggrippino@Envy-LM19-64:~$ docker service create --name proxy_nocheck -p 80:80 -p 443:443 -p 8080:8080 --network proxy -e MODE=swarm --health-cmd ""  dockerflow/docker-flow-proxy
1sj15vp72sfze8fa2qilivalu
overall progress: 0 out of 1 tasks
1/1: starting
^COperation continuing in background.
Use `docker service ps 1sj15vp72sfze8fa2qilivalu` to check progress.



vaggrippino@Envy-LM19-64:~$ docker service ps 1sj15vp72sfze8fa2qilivalu
ID                  NAME                  IMAGE                                 NODE                DESIRED STATE       CURRENT STATE               ERROR                              PORTS
jt68lwtpeaii        proxy_nocheck.1       dockerflow/docker-flow-proxy:latest   node-2              Ready               Ready 1 second ago
3wb0e5uvvvmr         \_ proxy_nocheck.1   dockerflow/docker-flow-proxy:latest   node-2              Shutdown            Failed 1 second ago         "task: non-zero exit (137): do…"
osr3cz6uatmz         \_ proxy_nocheck.1   dockerflow/docker-flow-proxy:latest   node-2              Shutdown            Failed 35 seconds ago       "task: non-zero exit (137): do…"
7q6d2gggsmdz         \_ proxy_nocheck.1   dockerflow/docker-flow-proxy:latest   node-2              Shutdown            Failed about a minute ago   "task: non-zero exit (137): do…"
qavn7cg663ky         \_ proxy_nocheck.1   dockerflow/docker-flow-proxy:latest   node-2              Shutdown            Failed about a minute ago   "task: non-zero exit (137): do…"



vaggrippino@Envy-LM19-64:~$ docker service logs -f proxy
no such task or service: proxy
vaggrippino@Envy-LM19-64:~$ ^Ccker service ps 1sj15vp72sfze8fa2qilivalu
vaggrippino@Envy-LM19-64:~$ docker service logs -f proxy_nocheck
proxy_nocheck.1.r1j5nkzkutu6@node-1    | 2018/09/12 20:17:35 Starting HAProxy
proxy_nocheck.1.r1j5nkzkutu6@node-1    | 2018/09/12 20:17:35 Getting certs from http://202.71.99.195:8080/v1/docker-flow-proxy/certs
proxy_nocheck.1.7q6d2gggsmdz@node-2    | 2018/09/12 20:15:09 Starting HAProxy
proxy_nocheck.1.osr3cz6uatmz@node-2    | 2018/09/12 20:15:42 Starting HAProxy
proxy_nocheck.1.3wb0e5uvvvmr@node-2    | 2018/09/12 20:16:15 Starting HAProxy
proxy_nocheck.1.jt68lwtpeaii@node-2    | 2018/09/12 20:16:49 Starting HAProxy
proxy_nocheck.1.jt68lwtpeaii@node-2    | 2018/09/12 20:16:49 Getting certs from http://202.71.99.195:8080/v1/docker-flow-proxy/certs
proxy_nocheck.1.7q6d2gggsmdz@node-2    | 2018/09/12 20:15:09 Getting certs from http://202.71.99.195:8080/v1/docker-flow-proxy/certs
proxy_nocheck.1.osr3cz6uatmz@node-2    | 2018/09/12 20:15:42 Getting certs from http://202.71.99.195:8080/v1/docker-flow-proxy/certs
proxy_nocheck.1.3wb0e5uvvvmr@node-2    | 2018/09/12 20:16:16 Getting certs from http://202.71.99.195:8080/v1/docker-flow-proxy/certs
proxy_nocheck.1.ggqusdw4wuau@node-3    | 2018/09/12 20:18:20 Starting HAProxy
proxy_nocheck.1.ggqusdw4wuau@node-3    | 2018/09/12 20:18:20 Getting certs from http://202.71.99.195:8080/v1/docker-flow-proxy/certs
^C

Starting the service without the overlay proxy seems to result in the same problem, but I wasn't able to view the logs (why?):

vaggrippino@Envy-LM19-64:~$ docker service create --name proxy_nooverlay -p 80:80 -p 443:443 -p 8080:8080 -e MODE=swarm dockerflow/docker-flow-proxy
zauybsnpyksb3e7knixonkk06
overall progress: 0 out of 1 tasks
1/1: starting
^COperation continuing in background.
Use `docker service ps zauybsnpyksb3e7knixonkk06` to check progress.



vaggrippino@Envy-LM19-64:~$ docker service ps zauybsnpyksb3e7knixonkk06
ID                  NAME                    IMAGE                                 NODE                DESIRED STATE       CURRENT STATE               ERROR                              PORTS
p60p0swwth7t        proxy_nooverlay.1       dockerflow/docker-flow-proxy:latest   node-2              Running             Starting 12 seconds ago
11jh9bkmwqoe         \_ proxy_nooverlay.1   dockerflow/docker-flow-proxy:latest   node-2              Shutdown            Failed 17 seconds ago       "task: non-zero exit (137): do…"
uok0wlqlqj0x         \_ proxy_nooverlay.1   dockerflow/docker-flow-proxy:latest   node-2              Shutdown            Failed 50 seconds ago       "task: non-zero exit (137): do…"
uuby6a1rxo5d         \_ proxy_nooverlay.1   dockerflow/docker-flow-proxy:latest   node-2              Shutdown            Failed about a minute ago   "task: non-zero exit (137): do…"



vaggrippino@Envy-LM19-64:~$ docker logs -f proxy_nooverlay
Error: No such container: proxy_nooverlay



vaggrippino@Envy-LM19-64:~$ docker service ls
ID                  NAME                MODE                REPLICAS            IMAGE                                 PORTS
jeotxn6w9ll9        go-demo             replicated          1/1                 vfarcic/go-demo:1.0     
3vonoya36a5u        go-demo-db          replicated          1/1                 mongo:3.2.10            
zauybsnpyksb        proxy_nooverlay     replicated          0/1                 dockerflow/docker-flow-proxy:latest   *:80->80/tcp, *:443->443/tcp, *:8080->8080/tcp
xrqyomupmarv        util                global              3/3                 alpine:latest     

[thomasjpfan]

The issue is how its attempting to get certs from 202.71.99.195. In the beginning, DFP tries to get the certs from other DFP instances. This IP should be the ip given by the proxy overlay network. Can you post the output of the following?

docker service create --name proxy -p 80:80 -p 443:443 -p 8080:8080 \
--network proxy -e MODE=swarm dockerflow/docker-flow-proxy
docker network inspect proxy

[VAggrippino]

Even with only one node, it seems like the same problem, but I can't view the logs again and I don't understand what changed...

vaggrippino@Envy-LM19-64:~$ docker-machine create -d virtualbox node-1
Running pre-create checks...
Creating machine...
(node-1) Copying /home/vaggrippino/.docker/machine/cache/boot2docker.iso to /home/vaggrippino/.docker/machine/machines/node-1/boot2docker.iso...
(node-1) Creating VirtualBox VM...
(node-1) Creating SSH key...
(node-1) Starting the VM...
(node-1) Check network to re-create if needed...
(node-1) Waiting for an IP...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...

This machine has been allocated an IP address, but Docker Machine could not
reach it successfully.

SSH for the machine should still work, but connecting to exposed ports, such as
the Docker daemon port (usually <ip>:2376), may not work properly.

You may need to add the route manually, or use another related workaround.

This could be due to a VPN, proxy, or host file configuration issue.

You also might want to clear any VirtualBox host only interfaces you are not using.
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env node-1


vaggrippino@Envy-LM19-64:~$ eval $(docker-machine env node-1)
vaggrippino@Envy-LM19-64:~$ docker service create --name proxy -p 80:80 -p 443:443 -p 8080:8080 -e MODE=swarm dockerflow/docker-flow-proxy
Error response from daemon: This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again.


vaggrippino@Envy-LM19-64:~$ docker swarm init --advertise-addr $(docker-machine ip node-1)
Swarm initialized: current node (q3yqh57heyo4farsgd2hp4i1l) is now a manager.

To add a worker to this swarm, run the following command:

    docker swarm join --token SWMTKN-1-341r6m4vaujcbdvfie7vyhkpcguuwik5r54114pmzjff2gwsfk-6tl6t44ky6838m6i9czdfkysl 192.168.99.100:2377

To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.

vaggrippino@Envy-LM19-64:~$ docker service create --name proxy -p 80:80 -p 443:443 -p 8080:8080 -e MODE=swarm dockerflow/docker-flow-proxy
veg99raaf377bc14g5jqyb54d
overall progress: 0 out of 1 tasks
1/1: starting
^COperation continuing in background.
Use `docker service ps veg99raaf377bc14g5jqyb54d` to check progress.
vaggrippino@Envy-LM19-64:~$ docker service ps veg99raaf377bc14g5jqyb54d
ID                  NAME                IMAGE                                 NODE                DESIRED STATE       CURRENT STATE             ERROR                              PORTS
mbi0x7s5v7hj        proxy.1             dockerflow/docker-flow-proxy:latest   node-1              Running             Starting 17 seconds ago
wf1n131agwoh         \_ proxy.1         dockerflow/docker-flow-proxy:latest   node-1              Shutdown            Failed 22 seconds ago     "task: non-zero exit (137): do…"
ix93hnb9qein         \_ proxy.1         dockerflow/docker-flow-proxy:latest   node-1              Shutdown            Failed 55 seconds ago     "task: non-zero exit (137): do…"


vaggrippino@Envy-LM19-64:~$ docker logs -f proxy
Error: No such container: proxy
vaggrippino@Envy-LM19-64:~$ docker service ls
ID                  NAME                MODE                REPLICAS            IMAGE                                 PORTS
veg99raaf377        proxy               replicated          0/1                 dockerflow/docker-flow-proxy:latest   *:80->80/tcp, *:443->443/tcp, *:8080->8080/tcp

[VAggrippino]

Here's the output of docker network inspect proxy:

vaggrippino@Envy-LM19-64:~$ docker network inspect proxy
[
    {
        "Name": "proxy",
        "Id": "ucw54qzj3qt0uwqh5rsz1o3oy",
        "Created": "2018-09-12T21:20:28.198647164Z",
        "Scope": "swarm",
        "Driver": "overlay",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "10.0.0.0/24",
                    "Gateway": "10.0.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "e91dfd53d1f493d269a14759803dbb946708f75d8c195358712b956c3422bef7": {
                "Name": "proxy.1.r92r989y7uqax2pwnecax1y6w",
                "EndpointID": "6e03327a7bd6f7a4972e22d4f961589660651255a44d5c08797c8431d350b8a8",
                "MacAddress": "02:42:0a:00:00:08",
                "IPv4Address": "10.0.0.8/24",
                "IPv6Address": ""
            },
            "lb-proxy": {
                "Name": "proxy-endpoint",
                "EndpointID": "f148f2d09e7fec094e6cbb380e9c917b9a1e7b29f8a9b1826e2d51f6fd1d340d",
                "MacAddress": "02:42:0a:00:00:03",
                "IPv4Address": "10.0.0.3/24",
                "IPv6Address": ""
            }
        },
        "Options": {
            "com.docker.network.driver.overlay.vxlanid_list": "4097"
        },
        "Labels": {},
        "Peers": [
            {
                "Name": "07ad1249d7c6",
                "IP": "192.168.99.100"
            }
        ]
    }
]

[VAggrippino]

I just realized that I dropped the service keyword from the docker command when I was trying to view the logs. I re-ran the service create commands and viewed the logs and got the same error messages as before.