Dynamic config permission denied; can't enable workflows

Self Hosted Retool
, , , ,
6

I also encountered the same issue. My workaround:

Create a Temporal.Dockerfile in the main folder (default is their retool-onpremise-master). Content:

FROM temporalio/auto-setup:1.23.1

USER root

RUN touch /etc/temporal/config/dynamicconfig/development-sql.yaml
RUN chown -R root:temporal /etc/temporal

On docker-compose.yml replace the original temporal section with below:

  temporal:
    container_name: temporal
    build:
      context: ./
      dockerfile: Temporal.Dockerfile
    env_file: ./docker.env
    environment:
      - DB=postgresql
      - POSTGRES_SEEDS=postgres
      - DYNAMIC_CONFIG_FILE_PATH=config/dynamicconfig/development-sql.yaml
      # To enable TLS between temporal and external postgres, set both below variables to true
      - SQL_TLS_ENABLED=false
      - SQL_TLS=false
      # Defined twice because temporal-server and temporal-sql-tool use different envvars
      - SQL_TLS_DISABLE_HOST_VERIFICATION=true
      - SQL_HOST_VERIFICATION=false
    # image: tryretool/one-offs:retool-temporal-1.1.2
    networks:
      - intra-temporal-network
      - temporal-network
    ports:
      - "127.0.0.1:7233:7233"
    # volumes:
    #   - ./dynamicconfig:/etc/temporal/config/dynamicconfig

what it does is

  • to build the temporal container from the freshly created Temporal.Dockerfile instead of the virgin image from dockerhub
  • to disable the dynamicconfig volumns (which causes the issue)

However, I also encountered some other issues after this, if you guys have seen similar one while enabling workflow on self-host retool with self-host temporal and know the solution, please let me know: