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

No more + character in environment variable WATCHTOWER_NOTIFICATION_EMAIL_SUBJECTTAG #814

Closed
MilesTEG1 opened this issue Feb 6, 2021 · 4 comments

Comments

@MilesTEG1
Copy link

Describe the bug

  • character in environment variable WATCHTOWER_NOTIFICATION_EMAIL_SUBJECTTAG isn't present in the mail's object since the 8 January.

To Reproduce
Steps to reproduce the behavior:
Set this environnement variable like this :

      - WATCHTOWER_NOTIFICATION_EMAIL_SUBJECTTAG=[ Watchtower-DS920+ ]

Expected behavior
I expected to have the + character in my object message like this :
[ Watchtower-DS920 ] Watchtower updates on ...

Screenshots
image

image

Environment

  • Platform = Synology NAS DS920+
  • Architecture = amd64 (CPU = Intel Celeron J4125)
  • Docker version = 18.09.0-0513
  • I use Portainer CE 2.1.1 to create my container
Logs from running watchtower with the --debug option

time="2021-02-06T14:04:43+01:00" level=debug

time="2021-02-06T14:04:44+01:00" level=debug msg="Sleeping for a second to ensure the docker api client has been properly initialized."

time="2021-02-06T14:04:45+01:00" level=debug msg="Retrieving running containers"

time="2021-02-06T14:04:45+01:00" level=debug msg="There are no additional watchtower containers"

time="2021-02-06T14:04:45+01:00" level=debug msg="Watchtower HTTP API skipped."

time="2021-02-06T14:04:45+01:00" level=info msg="Starting Watchtower and scheduling first run: 2021-02-07 06:00:00 +0100 CET"

Additional context
Before the 8 January, the + character was present in my notification subject (see the screenshot). But since, it's not. I didn't change the docker-compose.yml file I'm using, except for the schedule.

Here the docker-compose.yml I'm using :

#
# Doc de Watchtower : https://containrrr.dev/watchtower/
# Dépôt GitHub : https://github.com/containrrr/watchtower/
#
---
version: "2.1"
services:
  watchtower:
    image: containrrr/watchtower:amd64-latest
    container_name: watchtower
    network_mode: bridge
    environment:
      - WATCHTOWER_NOTIFICATIONS=email
      #- WATCHTOWER_NOTIFICATIONS_LEVEL=debug
      - WATCHTOWER_CLEANUP=true
      - WATCHTOWER_REMOVE_VOLUMES=true
      - WATCHTOWER_DEBUG=true
      - WATCHTOWER_LABEL_ENABLE=true
      - WATCHTOWER_TIMEOUT=30s
      # Utiliser soit SCHEDULE soit INTERVAL (ce dernier en sec)
      # Pour SCHEDULE : https://crontab.guru/#0_9_*_*_*
      # Ajouter un 0 en premier pour les secondes : secondes | minutes | heures | jour du mois | mois | jour de la semaine
      - WATCHTOWER_SCHEDULE=0 0 6 * * *
      #- WATCHTOWER_POLL_INTERVAL=3000
      - TZ=Europe/Paris
      
      #####################################################################
      # Pour les notifications en emails :
      - WATCHTOWER_NOTIFICATION_EMAIL_SUBJECTTAG=[ Watchtower-DS920+ ]
      - WATCHTOWER_NOTIFICATION_EMAIL_FROM=my-Gmail-email
      - WATCHTOWER_NOTIFICATION_EMAIL_TO=my-Gmail-email
      - WATCHTOWER_NOTIFICATION_EMAIL_SERVER=smtp.gmail.com
      - WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT=587
      - WATCHTOWER_NOTIFICATION_EMAIL_SERVER_USER=my-Gmail-email
      - WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD=apasswordtomyemail
      - WATCHTOWER_NOTIFICATION_EMAIL_DELAY=2
      #####################################################################
    
    labels:
      - "com.centurylinklabs.watchtower.enable=true"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    restart: unless-stopped

@github-actions
Copy link

github-actions bot commented Feb 6, 2021

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! 🙏

@piksel
Copy link
Member

piksel commented Feb 6, 2021

That should be fixed in shoutrrr v0.4.1 which will be in the next watchtower release.

@MilesTEG1
Copy link
Author

Ho ! Cool :D
I didn't do something wrong 😃

@simskij simskij closed this as completed Apr 22, 2021
@ghost
Copy link

ghost commented Apr 22, 2021

To avoid important communication to get lost in a closed issues no one monitors, I'll go ahead and lock this issue. If you want to continue the discussion, please open a new issue. Thank you! 🙏🏼

@containrrr containrrr locked as resolved and limited conversation to collaborators Apr 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants