<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi!<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 24.10.2019 um 09:21 schrieb Robert Kisteleki <<a href="mailto:robert@ripe.net" class="">robert@ripe.net</a>>:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">I believe there will be demand for a docker version, so I'm happy that</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">it's emerging! The way I see it there are some issues to resolve:</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">* permanent storage of key material, so outside the container?</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">* how to handle upgrading if there's a new (upstream) available</span></div></blockquote></div><br class=""><div class="">The question I have is a more sustainable versioning overall. On GitHub is just the source code available but not the rpm.</div><div class=""><br class=""></div><div class="">Key is stored outside with the docker overlay2 driver or directly on the disk. I would prompt the users to make a backup from it. </div><div class="">Upgrading can handle another container, it just watches for a new version, pulls it, deletes the old container and is starting the new one. With CentOS at this time it is a good idea to keep the software inside docker up to date :)</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">Can you explain what problem you want to solve? If you want to "move"</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">your probe from one server to another as a one-off action, you can</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">always just install the new one, submit its key to us as a replacement</span><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">[almost implemented :-)] and stop the old instance.</span></blockquote><br class=""></div><div class="">Sure, but both solutions are producing the same end result. The same probe ID is reporting.</div><div class=""><br class=""></div><div class=""><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"></div><blockquote type="cite" class=""><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Happy to see progress on software probes :). I will try to deploy it on our raspberries on the weekend.</div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">My thoughts on the docker stuff, we should aim to make it run with alpine linux before we release an official container, because a CentOS container seems to be too bloated. </div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Storage outside of the container should be no problem, I suggest we make a docker-compose file to setup all the storage stuff etc.. If there is an upgrade script between versions we should run the upgrade script at every container start.</div></blockquote><br class=""></div><div class="">Hi Anika,</div><div class=""><br class=""></div><div class="">Any success with RPI?</div><div class=""><br class=""></div><div class="">The problem at this time is that we need tini for handling multiple running processes inside one container like cron, SSH, telnet, the pings and pongs, so implementing that into Alpine would also be an overhead :)</div><div class=""><br class=""></div><div class="">###</div> CGroup: /docker/XYZ/system.slice/atlas.service<br class=""> ├─ 28 /bin/sh /usr/local/atlas/bin/ATLAS<br class=""> ├─ 73 /usr/local/atlas/bb-13.3/usr/sbin/telnetd -b 127.0.0.1 -p 2023 -P /var/atlas-probe/run/telnetd-port2023-pid.vol<br class=""> ├─ 95 /usr/local/atlas/bb-13.3/bin/perd -c /var/atlas-probe/crons/main -A 9801 -P /var/atlas-probe/run/perd-main.pid.vol<br class=""> ├─ 97 /usr/local/atlas/bb-13.3/bin/eperd -c /var/atlas-probe/crons/7 -A 9807 -P /var/atlas-probe/run/perd-7.pid.vol -O /home/atlas/data/new/7 -i 7<br class=""> ├─ 98 /bin/sh /usr/local/atlas/bin/ATLAS<br class=""> ├─ 100 /usr/local/atlas/bb-13.3/bin/eooqd /var/atlas-probe/crons/oneoff -A 9809 -P /var/atlas-probe/run/eooqd.pid.vol -i 9<br class=""> ├─ 124 /usr/bin/ssh -o ServerAliveInterval 60 -o StrictHostKeyChecking yes -o UserKnownHostsFile /var/atlas-probe/.ssh/known_hosts -R 54453:127.0.0.1:2023 -L 8080:127.0.0.1:8080 -i /var/a...<br class=""><div class=""> └─11726 sleep 180</div><div class="">###</div><div class=""><br class=""></div><div class="">Afaik there is no upgrade needed? The only dependency we have inside Docker is the magic ssh key :)</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>