Are docker compose blueprints suppose to apply constantly?

[weiw11]

I'm testing out using docker compose labels to apply blueprints, but it's constantly applying the same blueprint, sometimes randomly.

I know it's suppose to apply when you rebuild, but even when I haven't touched the container at all, it'll still apply like from the 10:06:46 timestamp record to 10:10:05 in the screenshot below.

Does blueprints apply on any container status change, such as start, stop, redeploy?

Newt docker compose file

services:
  newt:
    image: fosrl/newt
    container_name: newt
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - DOCKER_SOCKET=/var/run/docker.sock
      - PANGOLIN_ENDPOINT=xxxxx
      - NEWT_ID=xxxxx
      - NEWT_SECRET=xxxxx

Service docker compose file

services:
  container_name:
    image: container_name/container_name:latest
    container_name: container_name
    restart: unless-stopped
    ports:
      - 'xxxx:xxxx'
    labels:
      # Proxy Resource Configuration
      - pangolin.proxy-resources.container_name.name=container_name
      - pangolin.proxy-resources.container_name.full-domain=sub.domain.tld
      - pangolin.proxy-resources.container_name.protocol=http
      - pangolin.proxy-resources.container_name.auth.sso-enabled=true
      - pangolin.proxy-resources.container_name.targets[0].method=http
      - pangolin.proxy-resources.container_name.targets[0].hostname=xxx.xxx.xxx.xxx
      - pangolin.proxy-resources.container_name.targets[0].port=xxxx

Blueprints page: This is the same service using the docker compose file above

[oschwartz10612]

Blueprints applies can be triggered from a change in the docker stack, from the newt restarting, or from visiting the resource in the dashboard. This is because when you visit the resource it tries to sync with the docker container. This has caused some confusion so I am open to changing it. Feel free to reopen if this does not answer the question.

[weiw11]

or from visiting the resource in the dashboard.

I think adding this to the docker section of blueprints in the documentation would be really helpful as I wasn't able to find this information easily. Searching on both github and discord yielded no results which led to this post.

This is because when you visit the resource it tries to sync with the docker container.

Would this update the compose file directly as well?

[oschwartz10612]

Can can do on the docs! If you want to PR that would be awesome as well! :} We never push anything into the compose, only read from what docker has running. Compose is not actually even necessary because it talks with the socket.

[weiw11]

Thanks! I'll look into it.

And just so I fully understand this, as the compose file won't be touched, the compose file would be the source of truth correct? It would essentially take the need off configuring on the UI to the compose file.

If user redeploys, the compose file blueprint would overwrite all configurations on Pangolin, making any modifications on the pangolin UI meaningless.

[oschwartz10612]

Yep thats right