"This stack was created outside of portainer"... but it was not

[LeVraiRoiDHyrule]

Ask a Question!

Hi,

I am trying to install Zrok through portainer stacks, using the following compose:

version: "3.7"
services:
    # set file ownership
  zrok-init:
    image: busybox
    container_name: zrok-init
    restart: unless-stopped
    networks:
      - zrok
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
    # matches uid:gid of "nobody" in zrok container image
    command: chown -Rc 65534:65534 /mnt/.zrok
    #user: root
    volumes:
      - ${CONFIG_FOLDER}/zrok:/mnt/.zrok

  # enable zrok environment
  zrok-enable:
    image: ${ZROK_CONTAINER_IMAGE:-docker.io/openziti/zrok}
    platform: "linux/arm64"
    container_name: zrok-enable
    restart: unless-stopped
    networks:
      - zrok
    depends_on:
      zrok-init:
        condition: service_completed_successfully
    entrypoint: zrok-enable.bash
    volumes:
      - ${CONFIG_FOLDER}/zrok:/mnt
    environment:
      STATE_DIRECTORY: /mnt
      ZROK_ENABLE_TOKEN:
      #ZROK_API_ENDPOINT:
      ZROK_ENVIRONMENT_NAME: docker-public-share

      PUID: ${PUID}
      PGID: ${PGID}
      TZ: ${TZ}

  # provision a temporary zrok frontend subdomain and start sharing the backend target
  zrok-share:
    image: ${ZROK_CONTAINER_IMAGE:-docker.io/openziti/zrok}
    platform: "linux/arm64"
    container_name: zrok-share
    restart: unless-stopped
    networks:
      - zrok
    #restart: no
    entrypoint: zrok-share.bash
    depends_on:
      zrok-enable:
        condition: service_completed_successfully
    volumes:
      - ${CONFIG_FOLDER}/zrok:/mnt
    environment:
      # internal configuration
      STATE_DIRECTORY: /mnt  # zrok homedir in container
      ZROK_FRONTEND_MODE: temp-public  # tells zrok-share.bash to create a temporary subdomain and share until exit

      # most relevant options
      ZROK_BACKEND_MODE: proxy  # web, caddy, drive, proxy
      ZROK_TARGET: http://zrok-test:9090  # backend target, is a path in container filesystem unless proxy mode
      ZROK_INSECURE:        # "--insecure" if proxy target has unverifiable TLS server certificate
      ZROK_OAUTH_PROVIDER:  # google, github
      ZROK_OATH_EMAILS:     # space-separated list of OAuth email addresses or @domain.tld to allow
      ZROK_BASIC_AUTH:      # username:password, mutually-exclusive with ZROK_OAUTH_PROVIDER

      # least relevant options
      ZROK_VERBOSE:           # "--verbose"
      ZROK_SHARE_OPTS:        # additional arguments to "zrok share public" command
      ZROK_FRONTENDS:         # "public"
      PFXLOG_NO_JSON: "true"  # suppress JSON logging format

      PUID: ${PUID}
      PGID: ${PGID}
      TZ: ${TZ}

      # demo server you can share with zrok
  zrok-test:
    image: ${ZROK_CONTAINER_IMAGE:-docker.io/openziti/zrok}
    platform: "linux/arm64"
    container_name: zrok-test
    command: test endpoint --address 0.0.0.0  # 9090
    restart: unless-stopped
    networks:
      - zrok
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}

networks:
  services:
    name: services
    external: true
  zrok:
    name: zrok
    ipam:
      driver: default
      config:
        - subnet: ${ZROK_IP}.0/24

And I don't understand why, but I apparently can't edit nor do anything with this stack from Portainer. It tells me it is because it has been created outside of Portainer, which is false.

That is the first time I have this issue. What could be the problem ? It probably is related to zrok containers but I can't find what it could be. Any idea of what containers could be doing that would cause this behaviour ?

Thanks in advance for any answer, have a great day

[Nick-Portainer]

Interesting, anything deployed via Portainer should not show up as limited, I am not familiar with Zrok. Could you let me know whta environment varibles you are using and how you are deploying it step by step so I can attempt to replicate?

[LeVraiRoiDHyrule]

Thanks for your answer.

I didn't set up any more env variables than the ones shown here. My placeholders are the following:

TZ=Europe/Zurich
PUID=1000
PGID=1000
CONFIG_FOLDER=/storage/dockercontainers
ZROK_IP=172.19.0

For the deployment, I simply create a new stack using the compose and the placeholders, no extra step. I just have an already existing "services" network that is not used in this example so you can remove it from networks.

[LeVraiRoiDHyrule]

Hi, if someone has an idea of what the problem could be, I would be very interested. I am stuck with this stack that I can't edit and it's a bit irritating to have to delete and recreate it all each time I need to do a small modification. Have a nice day !

[LeVraiRoiDHyrule]

Hi, I found out that ghcr.io/zitadel/zitadel is affected the exact same way as docker.io/openziti/zrok. I tried all methods from here https://www.benjaminrancourt.ca/how-to-solve-a-limited-stack-in-portainer/ but none is having any effect. I gave up on zrok because there was better solution but this time, Zitadel is really something I would need.

[Nick-Portainer]

I have just tested with Zitadel and confirmed it was working as expected:

What are you steps for deploying your stack? Also your Portainer version and are you deploying to an agent or to the Portainer server node?

[Nick-Portainer]

@LeVraiRoiDHyrule Are you still facing this issue?