watchtower question

    • watchtower question

      TechnoDadLife wrote:



      Today, we will install Watchtower into a Openmediavault docker. Watchtower will then automatically update our other dockers.
      Hi!
      Thanks a lot again for your video tutorial! They are really helpful!
      Just one question: in the status section of watchtower I keep getting "restarting(0) X seconds ago"and it will reset every minute. Is it normal? if not, how can I solve it?
      Intel G4400 - Asrock H170M Pro4S - Syba SI-PEX40064 Marvell 88SE9125 - 8GB ram - Corsair VS350W - 2X6TB Seagate Ironwolf - 4x2TB WD Enterprise
      OMV 4.1.17 - Kernel 4.18 backport 3 - omvextrasorg 4.1.2
    • Blabla wrote:

      TechnoDadLife wrote:



      Today, we will install Watchtower into a Openmediavault docker. Watchtower will then automatically update our other dockers.
      Hi!Thanks a lot again for your video tutorial! They are really helpful!
      Just one question: in the status section of watchtower I keep getting "restarting(0) X seconds ago"and it will reset every minute. Is it normal? if not, how can I solve it?
      No, it's NOT normal and indicate some type of problem or bad configuration.

      delete your actual watchtower docker and recreate, if still restart, revise log, perhaps have permission problem.
      OMV 4.1.11 x64 on a HP T510, 16GB CF as Boot Disk & 32GB SSD 2,5" disk for Data, 4 GB RAM, CPU VIA EDEN X2 U4200 is x64 at 1GHz

      Post: HPT510 SlimNAS ; HOWTO Install Pi-Hole ; HOWTO install MLDonkey ; HOHTO Install ZFS-Plugin ; OMV_OldGUI ; ShellinaBOX ;
      Dockers: MLDonkey ; PiHole ; weTTY
      Videos: @TechnoDadLife
    • Deleted and recreated it, still have "restating(0) X seconds ago".
      I looked inside the log but this is all I found:

      Source Code

      1. watchtower version 0.3.0 - fbf6c0d620cd1c1c6a3b66cb6cd2280ffe073c43 - 2018-03-02T15:09:04Z
      2. watchtower version 0.3.0 - fbf6c0d620cd1c1c6a3b66cb6cd2280ffe073c43 - 2018-03-02T15:09:04Z
      3. watchtower version 0.3.0 - fbf6c0d620cd1c1c6a3b66cb6cd2280ffe073c43 - 2018-03-02T15:09:04Z
      4. watchtower version 0.3.0 - fbf6c0d620cd1c1c6a3b66cb6cd2280ffe073c43 - 2018-03-02T15:09:04Z
      5. watchtower version 0.3.0 - fbf6c0d620cd1c1c6a3b66cb6cd2280ffe073c43 - 2018-03-02T15:09:04Z
      6. watchtower version 0.3.0 - fbf6c0d620cd1c1c6a3b66cb6cd2280ffe073c43 - 2018-03-02T15:09:04Z
      7. watchtower version 0.3.0 - fbf6c0d620cd1c1c6a3b66cb6cd2280ffe073c43 - 2018-03-02T15:09:04Z
      8. watchtower version 0.3.0 - fbf6c0d620cd1c1c6a3b66cb6cd2280ffe073c43 - 2018-03-02T15:09:04Z
      9. watchtower version 0.3.0 - fbf6c0d620cd1c1c6a3b66cb6cd2280ffe073c43 - 2018-03-02T15:09:04Z
      10. watchtower version 0.3.0 - fbf6c0d620cd1c1c6a3b66cb6cd2280ffe073c43 - 2018-03-02T15:09:04Z


      This is the syslog instead:

      Source Code

      1. Jan 6 19:02:57 delibird liblogging-stdlog: [origin software="rsyslogd" swVersion="8.24.0" x-pid="1094" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
      2. Jan 6 19:03:01 delibird CRON[12637]: (root) CMD ( test -x /usr/sbin/wakealarm && /usr/sbin/wakealarm > /dev/null 2>&1)
      3. Jan 6 19:03:40 delibird containerd[1185]: time="2019-01-06T19:03:40.560873836+01:00" level=info msg="shim containerd-shim started" address="/containerd-shim/moby/da1e654dc990dab7a69dd75f7882af732a73c8474c68e1bc32b7578556f13aac/shim.sock" debug=false pid=13089
      4. Jan 6 19:03:40 delibird containerd[1185]: time="2019-01-06T19:03:40.818119484+01:00" level=info msg="shim reaped" id=da1e654dc990dab7a69dd75f7882af732a73c8474c68e1bc32b7578556f13aac
      5. Jan 6 19:03:40 delibird dockerd[1101]: time="2019-01-06T19:03:40.828655121+01:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
      6. Jan 6 19:04:01 delibird CRON[13382]: (root) CMD ( test -x /usr/sbin/wakealarm && /usr/sbin/wakealarm > /dev/null 2>&1)
      7. Jan 6 19:04:40 delibird containerd[1185]: time="2019-01-06T19:04:40.853692332+01:00" level=info msg="shim containerd-shim started" address="/containerd-shim/moby/da1e654dc990dab7a69dd75f7882af732a73c8474c68e1bc32b7578556f13aac/shim.sock" debug=false pid=13752
      8. Jan 6 19:04:41 delibird containerd[1185]: time="2019-01-06T19:04:41.237514079+01:00" level=info msg="shim reaped" id=da1e654dc990dab7a69dd75f7882af732a73c8474c68e1bc32b7578556f13aac
      9. Jan 6 19:04:41 delibird dockerd[1101]: time="2019-01-06T19:04:41.247592594+01:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
      10. Jan 6 19:05:01 delibird CRON[13989]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)

      This is the ID of watchtower: da1e654dc990
      Intel G4400 - Asrock H170M Pro4S - Syba SI-PEX40064 Marvell 88SE9125 - 8GB ram - Corsair VS350W - 2X6TB Seagate Ironwolf - 4x2TB WD Enterprise
      OMV 4.1.17 - Kernel 4.18 backport 3 - omvextrasorg 4.1.2
    • raulfg3 wrote:

      Blabla wrote:

      TechnoDadLife wrote:



      Today, we will install Watchtower into a Openmediavault docker. Watchtower will then automatically update our other dockers.
      Hi!Thanks a lot again for your video tutorial! They are really helpful!Just one question: in the status section of watchtower I keep getting "restarting(0) X seconds ago"and it will reset every minute. Is it normal? if not, how can I solve it?
      No, it's NOT normal and indicate some type of problem or bad configuration.
      delete your actual watchtower docker and recreate, if still restart, revise log, perhaps have permission problem.
      Each time I had a similar problem with docker containers, I traced it back to a permission issue.
      Air Conditioners are a lot like PC's... They work great until you open Windows.

    • KM0201 wrote:

      raulfg3 wrote:

      No, it's NOT normal and indicate some type of problem or bad configuration.delete your actual watchtower docker and recreate, if still restart, revise log, perhaps have permission problem.
      Each time I had a similar problem with docker containers, I traced it back to a permission issue.
      Do I need to give at the docker user some particular permission to have watchtower working right?
      Intel G4400 - Asrock H170M Pro4S - Syba SI-PEX40064 Marvell 88SE9125 - 8GB ram - Corsair VS350W - 2X6TB Seagate Ironwolf - 4x2TB WD Enterprise
      OMV 4.1.17 - Kernel 4.18 backport 3 - omvextrasorg 4.1.2
    • Blabla wrote:

      KM0201 wrote:

      raulfg3 wrote:

      No, it's NOT normal and indicate some type of problem or bad configuration.delete your actual watchtower docker and recreate, if still restart, revise log, perhaps have permission problem.
      Each time I had a similar problem with docker containers, I traced it back to a permission issue.
      Do I need to give at the docker user some particular permission to have watchtower working right?
      Well you need to make sure the docker user has read/write access on all the folders it's going to need check/update.
      Air Conditioners are a lot like PC's... They work great until you open Windows.

    • well, I'm pretty sure that dockeruser doesn't have R/W access at those folders :/ How can I know which folders is using? is it possible to have watchtower use root users?
      Intel G4400 - Asrock H170M Pro4S - Syba SI-PEX40064 Marvell 88SE9125 - 8GB ram - Corsair VS350W - 2X6TB Seagate Ironwolf - 4x2TB WD Enterprise
      OMV 4.1.17 - Kernel 4.18 backport 3 - omvextrasorg 4.1.2
    • Actually looking at it, he didn't even set it up as a docker user..

      I just followed his instructions and it works just fine for me.

      Edit: Where are your containers stored? I've got mine under /sharedfolders , which unless you've done something really different most users will have access to.
      Air Conditioners are a lot like PC's... They work great until you open Windows.

    • His instructions definitely work, I just checked again and refreshed, and it updated Calibre.

      From the watchtower logs:

      Source Code

      1. time="2019-01-06T08:38:21-10:00" level=info msg="First run: 2019-01-06 08:43:21 -1000 HST"
      2. time="2019-01-06T08:43:36-10:00" level=info msg="Found new linuxserver/calibre-web:latest image (sha256:8289e4c014d138449c18490e0f0663a3c5178d8d82708217b3f512958e1b2889)"
      3. time="2019-01-06T08:43:36-10:00" level=info msg="Stopping /calibre (285ff1c0fbe49c9eec763c71233e20527de16fb3259187fd8e80efcedb378ae8) with SIGTERM"
      4. time="2019-01-06T08:43:41-10:00" level=info msg="Creating /calibre"
      Air Conditioners are a lot like PC's... They work great until you open Windows.

    • KM0201 wrote:

      Actually looking at it, he didn't even set it up as a docker user..

      I just followed his instructions and it works just fine for me.

      Edit: Where are your containers stored? I've got mine under /sharedfolders , which unless you've done something really different most users will have access to.
      They are in theyr default folder, I never changed where docker should download and use the image.
      Looking in the detail of running docker the path should be:
      /var/lib/docker/containers/

      I'm now looking for the right command to ive dockeruser the right permission to that folder

      P.S. why are so many of my post getting blocked? :(
      Intel G4400 - Asrock H170M Pro4S - Syba SI-PEX40064 Marvell 88SE9125 - 8GB ram - Corsair VS350W - 2X6TB Seagate Ironwolf - 4x2TB WD Enterprise
      OMV 4.1.17 - Kernel 4.18 backport 3 - omvextrasorg 4.1.2

      The post was edited 1 time, last by Blabla ().

    • Blabla wrote:

      KM0201 wrote:

      Actually looking at it, he didn't even set it up as a docker user..

      I just followed his instructions and it works just fine for me.

      Edit: Where are your containers stored? I've got mine under /sharedfolders , which unless you've done something really different most users will have access to.
      They are in theyr default folder, I never changed where docker should download and use the image.Looking in the detail of running docker the path should be:
      /var/lib/docker/containers/

      I'm now looking for the right command to ive dockeruser the right permission to that folder

      That might be your issue... I created a shared folder on my data drive (ie 'Containers') and all my containers are there... obviously a user has read/write access there. Same with all the config files, I keep them all under /sharedfolders/Appconfig/config
      Air Conditioners are a lot like PC's... They work great until you open Windows.

    • I went into the folder and tried to give them access:

      Source Code

      1. root@delibird:/var/lib/docker# setfacl -R -m u:1000:rwx containers
      2. root@delibird:/var/lib/docker# ls -ld containers
      3. drwxrwx---+ 9 root root 4096 Jan 6 19:12 containers

      the UID 1000 is the one of dockersuser

      I'm using the default path for every docker..

      Source Code

      1. /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
      This is what I have if I try to run a new container or I try to modify the already existing ones
      Intel G4400 - Asrock H170M Pro4S - Syba SI-PEX40064 Marvell 88SE9125 - 8GB ram - Corsair VS350W - 2X6TB Seagate Ironwolf - 4x2TB WD Enterprise
      OMV 4.1.17 - Kernel 4.18 backport 3 - omvextrasorg 4.1.2
    • Blabla wrote:

      I went into the folder and tried to give them access:

      Source Code

      1. root@delibird:/var/lib/docker# setfacl -R -m u:1000:rwx containers
      2. root@delibird:/var/lib/docker# ls -ld containers
      3. drwxrwx---+ 9 root root 4096 Jan 6 19:12 containers
      the UID 1000 is the one of dockersuser

      I'm using the default path for every docker..

      Source Code

      1. /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
      This is what I have if I try to run a new container or I try to modify the already existing ones
      Honestly, I have no idea on that one, that is the strangest looking directory I've ever saw and does not exist on my system.
      Air Conditioners are a lot like PC's... They work great until you open Windows.

    • KM0201 wrote:

      Blabla wrote:

      I went into the folder and tried to give them access:

      Source Code

      1. root@delibird:/var/lib/docker# setfacl -R -m u:1000:rwx containers
      2. root@delibird:/var/lib/docker# ls -ld containers
      3. drwxrwx---+ 9 root root 4096 Jan 6 19:12 containers
      the UID 1000 is the one of dockersuser

      I'm using the default path for every docker..

      Source Code

      1. /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
      This is what I have if I try to run a new container or I try to modify the already existing ones
      Honestly, I have no idea on that one, that is the strangest looking directory I've ever saw and does not exist on my system.
      Since I was already planning to create a dedicate partition for docker+apps, there is some way move an already existing docker to an other folder?
      Can you please show me how you configured your containers to use them on an ther folder?
      Intel G4400 - Asrock H170M Pro4S - Syba SI-PEX40064 Marvell 88SE9125 - 8GB ram - Corsair VS350W - 2X6TB Seagate Ironwolf - 4x2TB WD Enterprise
      OMV 4.1.17 - Kernel 4.18 backport 3 - omvextrasorg 4.1.2

      The post was edited 1 time, last by Blabla ().

    • gderf wrote:

      How do you have the Watchtower container Restart policy set?

      Never set this to Always until you have first solved any problems.
      Right now is on "no" and I can't even start it :( When used "unless stopped" I got that error
      Intel G4400 - Asrock H170M Pro4S - Syba SI-PEX40064 Marvell 88SE9125 - 8GB ram - Corsair VS350W - 2X6TB Seagate Ironwolf - 4x2TB WD Enterprise
      OMV 4.1.17 - Kernel 4.18 backport 3 - omvextrasorg 4.1.2
    • Blabla wrote:

      Thanks :) I don't know why even if I gave permission at dockeruser it seems to not work :(
      Yeah, if you followed the tutorial, you skipped a step on where to put your containers. I'm assuming you have your /config folders under /shared folders somewhere, as they should be there to. I used vbox and moved a working deluge container from /var/lib/docker to a folder i created under /sharedfolders ("Containers)... When I try to create a docker (by pointing at the new containers folder).. I get either an invalid argument error, or some other error. I'm pretty sure I'm doing something wrong here.

      I'll have to look at it further... Or (what did work)...

      Download a clean image again
      Run it just like you were adding a new docker (add all your user info, folder locations, etc.) in the setup page. When you create the /config folder, point it at the /config folder for that container.

      As long as you point it at an existing config folder... when you log into whatever service it is, it will be exactly the same. Same passwords, etc.
      Air Conditioners are a lot like PC's... They work great until you open Windows.