# Zrok and Portainer

**URL:** <https://openziti.discourse.group/t/zrok-and-portainer/1941>\
**Category:** zrok\
**Created:** [December 23, 2023, 11:07am UTC](https://openziti.discourse.group/t/zrok-and-portainer/1941 "2023-12-23T11:07:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SaladCesar](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/saladcesar/32/1640_2.png) [@SaladCesar](https://openziti.discourse.group/u/SaladCesar)\
**Post date:** [December 23, 2023, 11:07am UTC](https://openziti.discourse.group/t/zrok-and-portainer/1941/1 "2023-12-23T11:07:35Z")

</div>

Hi,  
I am using Zrok in Docker, using Portainer to edit my docker compose files. But I'm having a problem that is Docker/Portainer related but that I never encountered elsewhere than with zrok containers. So I'm trying to find what's wrong with zrok containers but I can't find any help on Portainer forums.

My problem is that when I install zrok as a Docker Compose in Portainer, Portainer tells me that " This stack was created outside of portainer" and doesn't let me edit it. This normally happens when a compose is deployed using Docker CLI but in my case, I deployed it using Portainer.

My full docker compose is here : ["This stack was created outside of portainer"... but it was not · portainer · Discussion #10858 · GitHub](https://github.com/orgs/portainer/discussions/10858)

So I guess Zrok containers have a special argument or setting that make them un-editable by Portainer, but I can't find any solution.

Would you have an idea of what could be wrong ?  
Thanks in advance for any answer and have a great day.

---

<div class="post-metadata">

**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:** [December 23, 2023, 12:59pm UTC](https://openziti.discourse.group/t/zrok-and-portainer/1941/2 "2023-12-23T12:59:44Z")

</div>

I don't use portainer myself so I'm probably not too much help. I assume you've searched the Internet and [found references](https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://www.reddit.com/r/portainer/comments/slg0lg/this_stack_was_created_outside_portainer_despite/&ved=2ahUKEwi36YTdyqWDAxWeHzQIHclyCGEQFnoECCUQAQ&usg=AOvVaw2OPU2qm-Sxn54JZ8q3k-Bs) people saying: "This was my problem as well, stack name not matching the container name in the compose file caused this for me."?

I admit, I don't know what this means, myself. I dunno if there's anyone in the community using portainer yet that would comment here, but hopefully there is. Sorry I can't be more help. Have you looked at the [Docker file](https://github.com/openziti/zrok/blob/main/docker/images/zrok/Dockerfile) for any hints or tried to use it to build a container?

@qrkourier, have you ever tried portainer?

---

<div class="post-metadata">

**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:** [December 24, 2023, 8:02pm UTC](https://openziti.discourse.group/t/zrok-and-portainer/1941/3 "2023-12-24T20:02:35Z")

</div>

I haven't used Portainer yet at all. It appears to be a UI for managing Docker Compose projects and Kubernetes deployments. zrok provides a few Compose projects that should work perfectly with Portainer.

In the GitHub issue you linked I see your temporary zrok public share compose project and nothing about that seems problematic. You might also be interested in a reserved zrok public share which provides a permanent subdomain for your share, optionally a one that you picked as a "unique name" ([zrok frontdoor](https://docs.zrok.io/docs/guides/frontdoor/)).

In [the reddit thread](https://www.reddit.com/r/portainer/s/DqOGWT8L90) I speculated it could have to do with the network definition, but that didn't seem right to OP.

I agree it must be some compose option, perhaps the depends\_on directive, that Portainer doesn't support. Depending upon what property of the Compose project isn't supported by Portainer, it may be necessary to build a custom container image that performs some of the steps that are currently Compose services like init, enable, then share.
