# Docker-Compose Quickstart Setup - Edge Controller Issue **URL:** \ **Category:** General Questions\ **Created:** [June 22, 2022, 12:06am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601 "2022-06-22T00:06:56Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![anarchomoh](https://avatars.discourse-cdn.com/v4/letter/a/9de0a6/32.png) [@anarchomoh](https://openziti.discourse.group/u/anarchomoh)\ **Post date:** [June 22, 2022, 12:06am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/1 "2022-06-22T00:06:56Z")
Hi All I am trying to use the docker-compose quick-start to create my first network but have been waiting for the container to start for more than an hour. The terminal output continuously shows the below: ```auto openziti-ziti-controller-init-container-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-edge-router-wss-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-private-blue-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-edge-router-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-fabric-router-br-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-edge-router-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-private-blue-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-private-red-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-edge-router-wss-1 | waiting for https://ziti-edge-controller:1280 ``` have I missed something in the steps? Thanks for any help you can provide. ---
**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\ **Post date:** [June 22, 2022, 1:39am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/2 "2022-06-22T01:39:00Z")
Hi @anarchomoh, welcome to OpenZiti! Nice to see you on the forums and thanks for the post. That looks to me like the controller didn’t start. I don’t see it in the list there. Can you run ```auto docker logs openziti-ziti-controller ``` (assuming that was the container name, replace the name of the container if that’s not correct but it looks like it’ll be correct) Can you share what you did to start the docker environment? Did you curl/wget down the docker-compose.yml and .env files and then use `docker-compose -p openziti up`? The total time to start should be about 30 seconds to a minute depending on how fast your machine is. Also can you tell me what OS/docker version you’re using? It’s probably a situation we haven’t run into yet. Thanks! ---
**Author:** ![anarchomoh](https://avatars.discourse-cdn.com/v4/letter/a/9de0a6/32.png) [@anarchomoh](https://openziti.discourse.group/u/anarchomoh)\ **Post date:** [June 22, 2022, 1:56am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/3 "2022-06-22T01:56:19Z")
Hi @TheLumberjack. No worries. I ran the command and the output was: ```auto Error: No such container: openziti-ziti-controller ``` I did curl the compose.yml and the .env file. I used the standard `docker-compose up` command. I am using `Docker version 20.10.12, build tag v20.10.12` and my OS is Void Linux (no systemd). ---
**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\ **Post date:** [June 22, 2022, 2:00am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/4 "2022-06-22T02:00:18Z")
can you try: `docker ps -a | grep ziti-controller | grep -v init` and find the right one. I assume you only have a single one (i have two shown below) ```auto docker ps -a | grep ziti-controller | grep -v init 296982f26ac5 openziti/quickstart:latest "/openziti/scripts/r…" 21 minutes ago Exited (137) About a minute ago openziti_ziti-controller_1 8e53367d54b7 openziti/quickstart:latest "/openziti/scripts/r…" 5 days ago Exited (137) 21 minutes ago docker_ziti-controller_1 ``` Then run a `docker logs __put_right_container_name_here` ---
**Author:** ![anarchomoh](https://avatars.discourse-cdn.com/v4/letter/a/9de0a6/32.png) [@anarchomoh](https://openziti.discourse.group/u/anarchomoh)\ **Post date:** [June 22, 2022, 2:11am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/5 "2022-06-22T02:11:24Z")
Thanks. The output was: `d4a561d517a3 openziti/quickstart:latest "/openziti/scripts/r…" 39 seconds ago Exited (2) 36 seconds ago openziti-ziti-controller-1` I attached the logs command output. ![gscreenshot_2022-06-22-101044](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/1X/cfbdb78471ceb53d34bb598eed4f6d01bf05ca85.jpeg) ---
**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\ **Post date:** [June 22, 2022, 2:21am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/6 "2022-06-22T02:21:16Z")
woah a segfault is **REALLY** strange… i’ve literally never seen that myself when trying to run the ziti pki. You didn’t modify the docker compose file at all, right? Can you try just running the ‘raw’ container with: ```auto docker run --rm -it openziti/quickstart bash ``` and then once in that container type: ```auto ziti pki create ca whatever_this_doesnot_matter ``` ![image](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/1X/bc52d4b75cdef143e9d5bddca094a5b97cc10d4b.png) You have some kind of strange ‘permission’ issue going on in there. I might need help from someone with a deeper understanding of linux to figure this one out… run that command and follow up please. I don’t use “Void Linux” but do you know what version of GLIBC it uses? This might be a tough one… ---
**Author:** ![anarchomoh](https://avatars.discourse-cdn.com/v4/letter/a/9de0a6/32.png) [@anarchomoh](https://openziti.discourse.group/u/anarchomoh)\ **Post date:** [June 22, 2022, 2:26am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/7 "2022-06-22T02:26:30Z")
> [@TheLumberjack](#): > > `ziti pki create ca whatever_this_doesnot_matter` Thanks, no I did not modify the compose file or the .env at all. I have attached the output. ![gscreenshot_2022-06-22-102436](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/1X/c36648952c9db9540c068e9e96192c83ee12ab9a.jpeg) The glibc version is 2.32\_2 ---
**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\ **Post date:** [June 22, 2022, 2:38am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/8 "2022-06-22T02:38:43Z")
There are other “unknown pc” posts out there. ["Exception 0xc0000005", "runtime: unknown pc" on program exit with loaded windows dll · Issue #42593 · golang/go · GitHub](https://github.com/golang/go/issues/42593) am wondering if this is somehow a go issue… Right now - I don’t know what the issue is. we’ll keep digging. ---
**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\ **Post date:** [June 22, 2022, 2:44am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/9 "2022-06-22T02:44:58Z")
and a random reference here [runtime/cgo: pthread\_create failed: Operation not permitted · Issue #1501 · containers/skopeo · GitHub](https://github.com/containers/skopeo/issues/1501) to try `--security-opt seccomp=unconfined` … What happens when you run: ```auto docker run --security-opt seccomp=unconfined --rm -it openziti/quickstart bash ``` and try `ziti pki create ca whatever_this_doesnot_matter`? ---
**Author:** ![anarchomoh](https://avatars.discourse-cdn.com/v4/letter/a/9de0a6/32.png) [@anarchomoh](https://openziti.discourse.group/u/anarchomoh)\ **Post date:** [June 22, 2022, 2:50am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/10 "2022-06-22T02:50:29Z")
Thanks. I have attached the output: ![gscreenshot_2022-06-22-104826](https://global.discourse-cdn.com/free1/uploads/netfoundry/original/1X/2bfe1acdc6067f1ebccf2ba775c77f0d46e71ec9.jpeg) ---
**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\ **Post date:** [June 22, 2022, 2:57am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/11 "2022-06-22T02:57:22Z")
Well that is quite promising. It would seem that Void Linux has some security settings that docker doesn’t care for out of the box… Now I **want** you to modify the docker-compose.yml file. can you add this: ```auto security_opt: - seccomp:unconfined ``` to the ziti controller and see what happens? It should look like this in the file: ```auto version: '2.4' services: ziti-controller: image: "${ZITI_IMAGE}:${ZITI_VERSION}" security_opt: - seccomp:unconfined env_file: - ./.env ports: - "1280:1280" networks: zitiblue: aliases: - ziti-edge-controller zitired: aliases: - ziti-edge-controller volumes: - ziti-fs:/openziti entrypoint: - "/openziti/scripts/run-controller.sh" ``` then try a docker-compose up on that file… and don’t let it run for an hour if it’s not running 🙂 ---
**Author:** ![anarchomoh](https://avatars.discourse-cdn.com/v4/letter/a/9de0a6/32.png) [@anarchomoh](https://openziti.discourse.group/u/anarchomoh)\ **Post date:** [June 22, 2022, 3:11am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/12 "2022-06-22T03:11:32Z")
Thanks again. I modified the compose file but the result is the same: ```auto openziti-ziti-controller-init-container-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-edge-router-wss-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-private-red-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-private-blue-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-edge-router-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-controller-init-container-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-fabric-router-br-1 | waiting for https://ziti-edge-controller:1280 openziti-ziti-edge-router-wss-1 | waiting for https://ziti-edge-controller:1280 ``` ---
**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\ **Post date:** [June 22, 2022, 3:16am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/13 "2022-06-22T03:16:55Z")
Ok. I don’t want to keep asking you to run commands. I’ll get with one of the people here who knows linux a bit better. They might know how to fix this immediately. They won’t be online for about 8+ hours so - we’ll follow up in a bit. Thanks! We’ll get it working, I’m sure of it! 😃 ---
**Author:** ![gooseleggs](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/gooseleggs/32/450_2.png) [@gooseleggs](https://openziti.discourse.group/u/gooseleggs)\ **Post date:** [June 22, 2022, 1:18pm UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/14 "2022-06-22T13:18:35Z")
Hello @anarchomoh So, you can get this going. @TheLumberjack was correct - you need to add the ```auto security_opt: - seccomp:unconfined ``` against every service in the docker-compose file. Only doing the one server as @TheLumberjack has it will mean that the controller will start up, but the other components will fail with the same error. I have installed Void Linux and tested, and get to the first parts of the docker-compose example. Step 1 is to ensure that you machine has enough memory. I installed within Virtual box and 1G, 1 Proc did not cut it. I went to dual proc, 3G and had success. For sake of simplicity, here is the docker compose file in full: ```auto [root@void openziti]# cat docker-compose.yaml version: '2.4' services: ziti-controller: image: "${ZITI_IMAGE}:${ZITI_VERSION}" env_file: - ./.env ports: - "1280:1280" networks: zitiblue: aliases: - ziti-edge-controller zitired: aliases: - ziti-edge-controller volumes: - ziti-fs:/openziti security_opt: - seccomp:unconfined entrypoint: - "/openziti/scripts/run-controller.sh" ziti-controller-init-container: image: "${ZITI_IMAGE}:${ZITI_VERSION}" depends_on: - ziti-controller environment: - ZITI_CONTROLLER_RAWNAME="${ZITI_CONTROLLER_RAWNAME}" - ZITI_EDGE_CONTROLLER_RAWNAME="${ZITI_EDGE_CONTROLLER_RAWNAME}" env_file: - ./.env networks: zitiblue: aliases: - ziti-edge-controller-init-container zitired: aliases: - ziti-edge-controller-init-container security_opt: - seccomp:unconfined volumes: - ziti-fs:/openziti entrypoint: - "/openziti/scripts/access-control.sh" ziti-edge-router: image: "${ZITI_IMAGE}:${ZITI_VERSION}" depends_on: - ziti-controller environment: - ZITI_CONTROLLER_RAWNAME="${ZITI_CONTROLLER_RAWNAME}" - ZITI_EDGE_CONTROLLER_RAWNAME="${ZITI_EDGE_CONTROLLER_RAWNAME}" - ZITI_EDGE_ROUTER_RAWNAME=ziti-edge-router - ZITI_EDGE_ROUTER_ROLES=public ports: - "3022:3022" security_opt: - seccomp:unconfined networks: - zitiblue - zitired volumes: - ziti-fs:/openziti entrypoint: /bin/bash command: "/openziti/scripts/run-router.sh edge" ziti-edge-router-wss: image: "${ZITI_IMAGE}:${ZITI_VERSION}" depends_on: - ziti-controller security_opt: - seccomp:unconfined environment: - ZITI_CONTROLLER_RAWNAME="${ZITI_CONTROLLER_RAWNAME}" - ZITI_EDGE_CONTROLLER_RAWNAME="${ZITI_EDGE_CONTROLLER_RAWNAME}" - ZITI_EDGE_ROUTER_RAWNAME=ziti-edge-router-wss - ZITI_EDGE_ROUTER_PORT=3023 - ZITI_EDGE_ROUTER_ROLES=public ports: - "3023:3023" networks: - zitiblue - zitired volumes: - ziti-fs:/openziti entrypoint: /bin/bash command: "/openziti/scripts/run-router.sh wss" ziti-fabric-router-br: image: "${ZITI_IMAGE}:${ZITI_VERSION}" depends_on: - ziti-controller environment: - ZITI_CONTROLLER_RAWNAME="${ZITI_CONTROLLER_RAWNAME}" - ZITI_EDGE_CONTROLLER_RAWNAME="${ZITI_EDGE_CONTROLLER_RAWNAME}" - ZITI_EDGE_ROUTER_RAWNAME=ziti-fabric-router-br #ports: # - 3024:3024 security_opt: - seccomp:unconfined networks: - zitiblue - zitired volumes: - ziti-fs:/openziti entrypoint: /bin/bash command: "/openziti/scripts/run-router.sh fabric" ziti-private-red: image: "${ZITI_IMAGE}:${ZITI_VERSION}" depends_on: - ziti-controller environment: - ZITI_CONTROLLER_RAWNAME="${ZITI_CONTROLLER_RAWNAME}" - ZITI_EDGE_CONTROLLER_RAWNAME="${ZITI_EDGE_CONTROLLER_RAWNAME}" - ZITI_EDGE_ROUTER_RAWNAME=ziti-private-red #ports: # - 3025:3025 security_opt: - seccomp:unconfined networks: - zitired volumes: - ziti-fs:/openziti entrypoint: /bin/bash command: "/openziti/scripts/run-router.sh private" ziti-private-blue: image: "${ZITI_IMAGE}:${ZITI_VERSION}" depends_on: - ziti-controller environment: - ZITI_CONTROLLER_RAWNAME="${ZITI_CONTROLLER_RAWNAME}" - ZITI_EDGE_CONTROLLER_RAWNAME="${ZITI_EDGE_CONTROLLER_RAWNAME}" - ZITI_EDGE_ROUTER_RAWNAME=ziti-private-blue #ports: # - 3026:3026 security_opt: - seccomp:unconfined networks: - zitiblue volumes: - ziti-fs:/openziti entrypoint: /bin/bash command: "/openziti/scripts/run-router.sh private" web-test-blue: image: crccheck/hello-world ports: - "80:8000" security_opt: - seccomp:unconfined networks: zitiblue: aliases: - web-test-blue - web-test.blue - web.test.blue ziti-console: image: openziti/zac environment: - ZAC_SERVER_CERT_CHAIN=/openziti/pki/ziti-controller-intermediate/certs/ziti-controller-server.cert - ZAC_SERVER_KEY=/openziti/pki/ziti-controller-intermediate/keys/ziti-controller-server.key ports: - "1408:1408" - "8443:8443" working_dir: /usr/src/app volumes: - ziti-fs:/openziti security_opt: - seccomp:unconfined networks: - zitiblue - zitired networks: zitired: driver: bridge zitiblue: driver: bridge volumes: ziti-fs: ``` As can be seen, this is the stock standard docker-compose with the additional config files. Before you start it all up, lets clear out your environment. I used docker-compose for everything, instead of using `docker run`, so if you have not installed `docker-compose` please do this (to follow along). In the folder where the docker-compose file is, please run `docker-compose down -v` to clean the system. Then please run `docker ps -a` and ensure there are no stopped ziti containers hanging around. If there is, run `docker-compose down` again. This should clear it all out. Now that is done, we should be good to go. Either type `docker-compose up` if you want to see all the logs scroll up, or `docker-compose up -d` to fork it into the background (can do `docker logs -f ` to see a particular containers logs. Wait a while (maybe a minute), then use `docker exec -it *docker-ziti-controller-name-1* /bin/bash` where _docker-ziti-controller-name-1_ is the name of the docker container, which can be found by `docker ps | grep controller`. Once there, you can continue with the tutorial. FWIW, here is the docker-exec from my console ```auto [root@void kelvins]# docker exec -it openziti-ziti-controller-1 /bin/bash adding /openziti/ziti-bin to the path ziti@9bf1fc0c0bf8:/openziti$ zitiLogin Token: 59260357-66b9-4157-8440-56af0abf0725 Saving identity 'default' to /openziti/ziti-cli.json ziti@9bf1fc0c0bf8:/openziti$ ziti edge list identities ╭────────────┬───────────────────────┬────────┬────────────╮ │ ID │ NAME │ TYPE │ ATTRIBUTES │ ├────────────┼───────────────────────┼────────┼────────────┤ │ .iq1lZDPVW │ ziti-edge-router-wss │ Router │ │ │ KdU6lZ3QaW │ ziti-fabric-router-br │ Router │ │ │ Q1v1Oh3PaW │ ziti-private-blue │ Router │ │ │ TcTvhVi2p │ Default Admin │ User │ │ │ VTC1OZ3PV │ ziti-edge-router │ Router │ │ │ WYs1OhDQaW │ ziti-private-red │ Router │ │ ╰────────────┴───────────────────────┴────────┴────────────╯ results: 1-6 of 6 ziti@9bf1fc0c0bf8:/openziti$ ziti edge list edge-routers ╭────────────┬───────────────────────┬────────┬───────────────┬──────┬───────────────────────╮ │ ID │ NAME │ ONLINE │ ALLOW TRANSIT │ COST │ ATTRIBUTES │ ├────────────┼───────────────────────┼────────┼───────────────┼──────┼───────────────────────┤ │ .iq1lZDPVW │ ziti-edge-router-wss │ true │ true │ 0 │ public │ │ KdU6lZ3QaW │ ziti-fabric-router-br │ true │ true │ 0 │ ziti-fabric-router-br │ │ Q1v1Oh3PaW │ ziti-private-blue │ true │ true │ 0 │ ziti-private-blue │ │ VTC1OZ3PV │ ziti-edge-router │ true │ true │ 0 │ public │ │ WYs1OhDQaW │ ziti-private-red │ true │ true │ 0 │ ziti-private-red │ ╰────────────┴───────────────────────┴────────┴───────────────┴──────┴───────────────────────╯ ``` I have not gone past this test. Have fun, and lets know how you go. ---
**Author:** ![qrkourier](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/qrkourier/32/52_2.png) [@qrkourier](https://openziti.discourse.group/u/qrkourier)\ **Post date:** [June 22, 2022, 3:15pm UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/15 "2022-06-22T15:15:36Z")
Can you determine whether your Void Linux install is set up to use musl or GNU libc? Also, please provide the output from `docker --version`. Apparently, older Docker doesn’t allow the newer `clone3` syscall that’s employed by `cgo` when spawning threads. ---
**Author:** ![anarchomoh](https://avatars.discourse-cdn.com/v4/letter/a/9de0a6/32.png) [@anarchomoh](https://openziti.discourse.group/u/anarchomoh)\ **Post date:** [June 22, 2022, 10:32pm UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/16 "2022-06-22T22:32:03Z")
> [@gooseleggs](#): > > `ziti edge list identities` thanks @gooseleggs, that worked perfectly. I will continue the rest of the tutorial video and am excited to setup the network. ---
**Author:** ![anarchomoh](https://avatars.discourse-cdn.com/v4/letter/a/9de0a6/32.png) [@anarchomoh](https://openziti.discourse.group/u/anarchomoh)\ **Post date:** [June 22, 2022, 11:00pm UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/17 "2022-06-22T23:00:37Z")
> [@qrkourier](#): > > `docker --version` Hi @qrkourier, it is glibc and the docker version is: `Docker version 20.10.12, build tag v20.10.12.` ---
**Author:** ![anarchomoh](https://avatars.discourse-cdn.com/v4/letter/a/9de0a6/32.png) [@anarchomoh](https://openziti.discourse.group/u/anarchomoh)\ **Post date:** [June 24, 2022, 9:30am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/18 "2022-06-24T09:30:19Z")
Hi Again I’m trying to add ZAC using the instructions on [docker-compose](https://openziti.github.io/ziti/quickstarts/zac/installation.html#using-docker-compose) but getting the error: `yaml: line 162: did not find expected key` when i do docker-compose up -d. What did I do incorrectly? ---
**Author:** ![gooseleggs](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/gooseleggs/32/450_2.png) [@gooseleggs](https://openziti.discourse.group/u/gooseleggs)\ **Post date:** [June 24, 2022, 11:33am UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/19 "2022-06-24T11:33:33Z")
Can you supply what is around line 162 and line 162 as well. Otherwise it is a bit hard to see what might be wrong. Couple of gotchas that may or may not help. Don’t use tabs to insert values unless it is done throughout the whole file. Always use spaces, and make sure that they line up correctly as indentation matters. That kind of error may be missing a : between name and variable. Some items requires quotes (") around the value, although I have used the code from that page recently and did not get a problem. ---
**Author:** ![gberl002](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/gberl002/32/333_2.png) [@gberl002](https://openziti.discourse.group/u/gberl002)\ **Post date:** [June 24, 2022, 1:32pm UTC](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601/20 "2022-06-24T13:32:49Z")
It sounds like there is some sort of indentation/formatting issue when the ziti-console service was copied and pasted the ziti-console service per the instructions. Can you share your docker-compose source (the entire contents of the file would be preferable) and make sure to leave the formatting exactly as it is in your docker-compose file? This would be important in figuring out exactly what the formatting issue is. In the meantime I’ll follow the instructions myself to see if I can replicate the issue as it may be some problem with the doc. [Next page](https://openziti.discourse.group/t/docker-compose-quickstart-setup-edge-controller-issue/601.md?page=2)