# Accessing remotely (Docker)

**URL:** <https://openziti.discourse.group/t/accessing-remotely-docker/2061>\
**Category:** General Questions\
**Created:** [February 8, 2024, 6:02pm UTC](https://openziti.discourse.group/t/accessing-remotely-docker/2061 "2024-02-08T18:02:36Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![jagauthier](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/jagauthier/32/1723_2.png) [@jagauthier](https://openziti.discourse.group/u/jagauthier)\
**Post date:** [February 15, 2024, 3:06pm UTC](https://openziti.discourse.group/t/accessing-remotely-docker/2061/21 "2024-02-15T15:06:26Z")

</div>

In the script `/var/openziti/scripts/run-router.sh` there is a bit of code several lines down:

```auto
# Wait until the file exists, then give one more second for the file to be completely written
until [-f "${ZITI_HOME}/ziti.env"]
do
     sleep 1
done

```

Seems to be an infinite wait. I wonder if the container I pulled is different from the one you did testing on.

Creating a bare minimum environment allowed my router to start, create certs, and enroll. Thanks again!

---

<div class="post-metadata">

**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:** [February 15, 2024, 3:24pm UTC](https://openziti.discourse.group/t/accessing-remotely-docker/2061/22 "2024-02-15T15:24:55Z")

</div>

@jagauthier thank you for finding this. This should have not been an infinite loop in the case of a failure to satisfy the condition. I am looking into this and filed an [issue](https://github.com/openziti/ziti/issues/1751).

[Previous page](https://openziti.discourse.group/t/accessing-remotely-docker/2061.md?page=1)