10 Apr 2024 |
@marioyd:matrix.yourdevice.ch | thought it automatically pulls newest version | 14:53:32 |
@marioyd:matrix.yourdevice.ch | not used to docker long | 14:53:38 |
AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | In reply to @marioyd:matrix.yourdevice.ch thought it automatically pulls newest version You could setup watchtower for this | 14:53:46 |
@marioyd:matrix.yourdevice.ch | updated and solved 🙏 | 14:53:59 |
AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | In reply to @marioyd:matrix.yourdevice.ch thought it automatically pulls newest version * You could setup watchtower for this (https://containrrr.dev/watchtower/) | 14:54:04 |
manwichmakesameal | You can use watchtower to auto-pull and notify. You can even have it restart the containers but personally, I don't like that. | 14:54:09 |
@marioyd:matrix.yourdevice.ch | just gotta run
docker run -d \
--name watchtower \
-v /var/run/docker.sock:/var/run/docker.sock \
containrrr/watchtower
| 14:55:16 |
@marioyd:matrix.yourdevice.ch | and thats all? | 14:55:19 |
manwichmakesameal | I would use a compose file, but that's just me. | 14:55:34 |
manwichmakesameal | But yes, that would get a functioning container of watchtower. | 14:55:53 |
manwichmakesameal | It'll pull and auto-restart ALL containers by default though. | 14:56:09 |
manwichmakesameal | services:
watchtower:
image: containrrr/watchtower
container_name: watchtower
volumes:
- /var/run/docker.sock:/var/run/docker.sock
environment:
WATCHTOWER_MONITOR_ONLY: 'true'
WATCHTOWER_NOTIFICATIONS: email
WATCHTOWER_NOTIFICATION_EMAIL_FROM: nope
WATCHTOWER_NOTIFICATION_EMAIL_TO: nope
WATCHTOWER_NOTIFICATION_EMAIL_SERVER: nope
WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT: 587
WATCHTOWER_NOTIFICATION_EMAIL_SERVER_USER: nope
WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD: ${WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD}
WATCHTOWER_NOTIFICATION_EMAIL_SUBJECTTAG: nope
restart: unless-stopped
You can put all of the environment variables in an env file but that's my compose file for watchtower.
| 14:58:04 |
@marioyd:matrix.yourdevice.ch | okay thanks, will look into this. Sorry i dont check so much github issues and here, allthough i should, but i guess
2024-04-10 14:55:14 UTC [info] 500 GET /api/v1/comments/jNQXAC9IVRw 362.62ms
ist still because of the comment issue still making trouble thus showing unhealthy containers?
| 14:58:09 |
AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | You can replace the health check with a different endpoint, for example: Replace http://127.0.0.1:3000/api/v1/comments/jNQXAC9IVRw with http://127.0.0.1:3000/api/v1/stats , then the container will show up as "healthy". | 15:00:42 |
@marioyd:matrix.yourdevice.ch | In reply to @alexpewmaster:nope.chat You can replace the health check with a different endpoint, for example: Replace http://127.0.0.1:3000/api/v1/comments/jNQXAC9IVRw with http://127.0.0.1:3000/api/v1/stats , then the container will show up as "healthy". updated this | 15:02:11 |
@marioyd:matrix.yourdevice.ch | thanks | 15:02:15 |
AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | Glad that we could help! | 15:02:28 |
@marioyd:matrix.yourdevice.ch | thanks again, much appreciated, sorry for my bobquestions. Need some time to dig into this better, Will set up the email notifications too, thanks for this hint!! | 15:03:54 |
AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | We all started somewhere, being a noob at some things doesn't make you stupid. You just gotta learn from the others who know better! | 15:04:53 |
@marioyd:matrix.yourdevice.ch | should be making no issues now:
https://invidious.yourdevice.ch
if you wanna test | 15:04:54 |
@marioyd:matrix.yourdevice.ch | public instance | 15:05:18 |
manwichmakesameal | In reply to @alexpewmaster:nope.chat We all started somewhere, being a noob at some things doesn't make you stupid. You just gotta learn from the others who know better! This. If you don't make mistakes, you don't learn. | 15:05:23 |
AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | I also bombarded this room with my problems earlier. I also managed to setup a public instance, even though I had a lot of issues during the process. | 15:06:53 |
@marioyd:matrix.yourdevice.ch | still need ipv6 rotation to be setup, sure I'll be coming back some days later haha 🤣 | 15:07:49 |
AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | In reply to @marioyd:matrix.yourdevice.ch still need ipv6 rotation to be setup, sure I'll be coming back some days later haha 🤣 Make sure to follow the Invidious docs! https://docs.invidious.io/ipv6-rotator/ | 15:08:20 |
@marioyd:matrix.yourdevice.ch | but I am already glad i have a multiple instance up and running | 15:08:25 |
@marioyd:matrix.yourdevice.ch | In reply to @alexpewmaster:nope.chat Make sure to follow the Invidious docs! https://docs.invidious.io/ipv6-rotator/ sure | 15:08:29 |
@marioyd:matrix.yourdevice.ch | noted this | 15:08:34 |
AlexPewMaster (moved to @alexpewmaster:reallyaweso.me) | And set it up as soon as possible! My instance got blocked with only 2 users using it! | 15:08:37 |
@marioyd:matrix.yourdevice.ch | really | 15:08:45 |