Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"com.centurylinklabs.watchtower.monitor-only=true" label is not working #1092

Open
b4too opened this issue Oct 13, 2021 · 5 comments
Open

"com.centurylinklabs.watchtower.monitor-only=true" label is not working #1092

b4too opened this issue Oct 13, 2021 · 5 comments

Comments

@b4too
Copy link

b4too commented Oct 13, 2021

Hello,

I am using the latest stable image of watchtower ( from 2021-04-24 ) wich works very fine on updating the containers labeled :
"com.centurylinklabs.watchtower.enable=true"
However I do not receive notifications from updatable containers labeled as such :
"com.centurylinklabs.watchtower.monitor-only=true"

My watchtower env configuration is the following :

      - WATCHTOWER_CLEANUP=true
      - WATCHTOWER_LABEL_ENABLE=true
      - WATCHTOWER_INCLUDE_RESTARTING=true
      - WATCHTOWER_SCHEDULE=0 0 2 * * *
      - WATCHTOWER_NOTIFICATIONS=gotify
      - WATCHTOWER_NOTIFICATION_GOTIFY_URL=
      - WATCHTOWER_NOTIFICATION_GOTIFY_TOKEN=
      - WATCHTOWER_NOTIFICATIONS_LEVEL=info

It runs on debian buster, docker version 20.10.9, build c2ea9bc

Thanks for your help.

@github-actions
Copy link

Hi there! 👋🏼 As you're new to this repo, we'd like to suggest that you read our code of conduct as well as our contribution guidelines. Thanks a bunch for opening your first issue! 🙏

@markfrancisonly
Copy link

"com.centurylinklabs.watchtower.monitor-only=true" label function isn't working without the WATCHTOWER_LABEL_ENABLE=true environment variable in my setup either

@mptpro
Copy link

mptpro commented Apr 3, 2023

doesn't work for me either. I have a Conainter that is built from a local image, and thus can't be updated. The problem is I have Watchtower set to notify via Telegram and I'm getting multiple messages daily of the "failed" update.

@janusn
Copy link

janusn commented May 31, 2023

The "com.centurylinklabs.watchtower.monitor-only=true" doesn't work on mine either.

  • Watchtower version: v1.5.3
  • Docker version 20.10.3, build 55f0773
  • Host OS: DSM 7.1.1-42962 Update 5

The container.yaml is:

---
# github page: https://github.com/khakers/go-subgen
version: "3.8"
services:
  subgen:
    container_name: subgen
    # image: ghcr.io/khakers/go-subgen:master
    build:
      context: https://github.com/khakers/go-subgen.git
    restart: unless-stopped
    ports:
      - "8095:8095"
    volumes:
      # Path must be identical to the path in your other services
      - "/volume2/Shared:/volume2/Shared:rw"
      # Models will be downloaded to this directory
      - "./config/models:/models:rw"
    environment:
      - MODEL_TYPE=small_en
      - TARGET_LANG=en
      - IGNORE_IF_EXISTING=true
      - MAX_CONCURRENCY=1
      - MODEL_DIR="/models/"
      - LOG_LEVEL=info
      - PORT=8095
      - SUBTITLE_NAME_TEMPLAT="{{.FileName}}.subgen.{{.Lang}}.{{.FileType}}"
      - WHISPER_CONF_THREADS=2
    labels:
      - "com.centurylinklabs.watchtower.enable=false"

It failed with the following message:

Could not do a head request for "subgen-subgen:latest", falling back to regular pull.
Reason: registry responded to head request with "401 Unauthorized", auth: "Bearer realm=\"[https://auth.docker.io/token\](https://auth.docker.io/token%5C)",service=\"[registry.docker.io](http://registry.docker.io/)\",scope=\"repository:library/subgen-subgen:pull\",error=\"insufficient_scope\""
Unable to update container "/subgen": Error response from daemon: pull access denied for subgen-subgen, repository does not exist or may require 'docker login': denied: requested access to the resource is denied. Proceeding to next.

@zoeperman
Copy link

Version 1.71
the com.centurylinklabs.watchtower.monitor-only="true" still isn't working
when putting this in my compose file the container doesn't get scanned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants