Organizr: Docker: Endless reboots, no install
Organizr Version: V 2.x
Branch: Master
Operating System: Docker
Problem Description:
Trying to install the docker container into my single host, single replication (basically just a normal docker) I keep getting endless reboots and it prevents itself from actual installing anything.
Error's aren't clear either.
Just to be clear:
All other containers in the same stack run perfectly fine.
Reproduction Steps:
- Install in docker swarm
- "profit"
Errors on screen? If so paste here:
Console output:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
-------------------------------------
GID/UID
-------------------------------------
User uid: 4242
User gid: 4242
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-install: executing...
-----------------------
| Updating Organizr |
-----------------------
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
-------------------------------------
GID/UID
-------------------------------------
User uid: 4242
User gid: 4242
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-install: executing...
-----------------------
| Updating Organizr |
-----------------------
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
Checking out files: 0% (7/4239)
Checking out files: 0% (10/4239)
Checking out files: 0% (32/4239)
Checking out files: 1% (43/4239)
Checking out files: 1% (55/4239)
Checking out files: 1% (76/4239)
Checking out files: 1% (80/4239)
Checking out files: 1% (83/4239)
Checking out files: 2% (85/4239)
Checking out files: 2% (89/4239)
Checking out files: 2% (112/4239)
Checking out files: 3% (128/4239)
Checking out files: 3% (135/4239)
Checking out files: 3% (139/4239)
Checking out files: 3% (143/4239)
Checking out files: 4% (170/4239)
Checking out files: 4% (173/4239)
Checking out files: 4% (209/4239)
Checking out files: 5% (212/4239)
Checking out files: 5% (232/4239)
Checking out files: 5% (237/4239)
Checking out files: 5% (242/4239)
Checking out files: 5% (248/4239)
Checking out files: 6% (255/4239)
Checking out files: 6% (272/4239)
Checking out files: 7% (297/4239)
Checking out files: 7% (301/4239)
Checking out files: 7% (304/4239)
Checking out files: 7% (309/4239)
Checking out files: 7% (337/4239)
Checking out files: 8% (340/4239)
Checking out files: 8% (360/4239)
Checking out files: 8% (373/4239)
Checking out files: 8% (376/4239)
Checking out files: 9% (382/4239)
Checking out files: 9% (384/4239)
Checking out files: 9% (407/4239)
Checking out files: 10% (424/4239)
Checking out files: 10% (437/4239)
Checking out files: 10% (440/4239)
Checking out files: 10% (443/4239)
Checking out files: 10% (464/4239)
Checking out files: 11% (467/4239)
Checking out files: 11% (493/4239)
Checking out files: 12% (509/4239)
Checking out files: 12% (532/4239)
Checking out files: 12% (534/4239)
Checking out files: 12% (538/4239)
Checking out files: 12% (543/4239)
Checking out files: 13% (552/4239)
Checking out files: 13% (569/4239)
Checking out files: 13% (586/4239)
Checking out files: 14% (594/4239)
Checking out files: 15% (636/4239)
Checking out files: 15% (641/4239)
Checking out files: 15% (644/4239)
Checking out files: 15% (653/4239)
Checking out files: 15% (659/4239)
Checking out files: 16% (679/4239)
Checking out files: 16% (684/4239)
Checking out files: 16% (695/4239)
Checking out files: 16% (699/4239)
Checking out files: 16% (719/4239)
Checking out files: 17% (721/4239)
Checking out files: 17% (758/4239)
Checking out files: 18% (764/4239)
Checking out files: 18% (789/4239)
Checking out files: 18% (792/4239)
Checking out files: 18% (795/4239)
Checking out files: 18% (803/4239)
Checking out files: 19% (806/4239)
Checking out files: 19% (833/4239)
Checking out files: 20% (848/4239)
Checking out files: 20% (860/4239)
Checking out files: 20% (865/4239)
Checking out files: 20% (867/4239)
Checking out files: 20% (871/4239)
Checking out files: 20% (875/4239)
Checking out files: 21% (891/4239)
Checking out files: 21% (897/4239)
Checking out files: 21% (901/4239)
Checking out files: 21% (907/4239)
Checking out files: 22% (933/4239)
Checking out files: 22% (938/4239)
Checking out files: 22% (963/4239)
Checking out files: 23% (975/4239)
Checking out files: 23% (990/4239)
Checking out files: 23% (1000/4239)
Checking out files: 23% (1006/4239)
Checking out files: 23% (1009/4239)
Checking out files: 24% (1018/4239)
Checking out files: 24% (1035/4239)
Checking out files: 25% (1060/4239)
Checking out files: 25% (1062/4239)
Checking out files: 25% (1067/4239)
Checking out files: 25% (1102/4239)
Checking out files: 26% (1103/4239)
Checking out files: 26% (1137/4239)
Checking out files: 27% (1145/4239)
Checking out files: 27% (1174/4239)
Checking out files: 28% (1187/4239)
Checking out files: 28% (1190/4239)
Checking out files: 28% (1207/4239)
Checking out files: 29% (1230/4239)
Checking out files: 29% (1231/4239)
Checking out files: 29% (1254/4239)
Checking out files: 29% (1266/4239)
Checking out files: 30% (1272/4239)
Checking out files: 30% (1301/4239)
Checking out files: 30% (1305/4239)
Checking out files: 30% (1309/4239)
Checking out files: 31% (1315/4239)
Checking out files: 31% (1332/4239)
Checking out files: 31% (1333/4239)
Checking out files: 31% (1337/4239)
Checking out files: 31% (1340/4239)
Checking out files: 31% (1353/4239)
Checking out files: 32% (1357/4239)
Checking out files: 32% (1381/4239)
Checking out files: 33% (1399/4239)
Checking out files: 33% (1422/4239)
Checking out files: 34% (1442/4239)
Checking out files: 34% (1456/4239)
Checking out files: 34% (1458/4239)
Checking out files: 34% (1461/4239)
Checking out files: 34% (1480/4239)
Checking out files: 35% (1484/4239)
Checking out files: 35% (1503/4239)
Checking out files: 35% (1507/4239)
Checking out files: 35% (1512/4239)
Checking out files: 36% (1527/4239)
Checking out files: 36% (1550/4239)
Checking out files: 37% (1569/4239)
Checking out files: 37% (1578/4239)
Checking out files: 37% (1582/4239)
Checking out files: 37% (1586/4239)
Checking out files: 37% (1594/4239)
Checking out files: 37% (1599/4239)
Checking out files: 38% (1611/4239)
Checking out files: 38% (1620/4239)
Checking out files: 39% (1654/4239)
Checking out files: 39% (1671/4239)
Checking out files: 39% (1684/4239)
Checking out files: 39% (1688/4239)
Checking out files: 40% (1696/4239)
Checking out files: 40% (1719/4239)
Checking out files: 41% (1738/4239)
Checking out files: 41% (1749/4239)
Checking out files: 41% (1761/4239)
Checking out files: 41% (1765/4239)
Checking out files: 41% (1769/4239)
Checking out files: 42% (1781/4239)
Checking out files: 42% (1795/4239)
Checking out files: 43% (1823/4239)
Checking out files: 43% (1827/4239)
Checking out files: 43% (1841/4239)
Checking out files: 43% (1843/4239)
Checking out files: 43% (1849/4239)
Checking out files: 44% (1866/4239)
Checking out files: 44% (1880/4239)
Checking out files: 45% (1908/4239)
Checking out files: 45% (1911/4239)
Checking out files: 45% (1926/4239)
Checking out files: 45% (1930/4239)
Checking out files: 45% (1933/4239)
N[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
-------------------------------------
GID/UID
-------------------------------------
User uid: 4242
User gid: 4242
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-install: executing...
-----------------------
| Updating Organizr |
-----------------------
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
Checking out files: 0% (18/4239)
Checking out files: 0% (20/4239)
Checking out files: 0% (23/4239)
Docker compose/stack code (only relevant portion):
organizr:
hostname: organizr
image: organizrtools/organizr-v2:latest
volumes:
- /var/data/autopirate/organizr:/config
environment:
- PUID=4242
- PGID=4242
restart: unless-stopped
networks:
- internal
- traefik_public
deploy:
labels:
- traefik.frontend.rule=Host:organizr.test.schouten-lebbing.nl
- traefik.docker.network=traefik_public
- traefik.port=80
Ornias1993
All 24 comments
@christronyxyocum @Roxedus any idea why it would exit or timeout which checking out files?
causefx
on 14 May 2020
My first thought is the healthcheck. Does the download process take longer than a minute?
Roxedus
on 14 May 2020
ahhh that would make sense. We would need to account for users with slow internet connections. I believe the repo is around 24 MB.
causefx
on 14 May 2020
Running over solutions in my head as we speak ;)
Roxedus
on 14 May 2020
Ah, yeah, that makes sense. Sorry guys, working with contractors at the house at the moment.
tronyx
on 14 May 2020
I think the issue is limited CPU/RAM not network speed. I doubt 500/500 fibre with 10gb SFP+ internal ( both verified) constitutes a “slow” connection.
That being said:
There seem to be two issues here:
- Lack of verbosity (it should scream TIMEOUT)
- The actual timeout (which could maybe be increased by env var?)
edit
Timeout=health check
I dont know if there is a way to add an additional check delay, is there?
Ornias1993
on 14 May 2020
Update:
I managed to get it installed, I simply increased the timeouts in the healthcheck, it indeed seems to be the healtcheck. I added this in de stack/compose file:
(which for sure would prevent any and all timeouts)
healthcheck:
interval: 60s
timeout: 30s
retries: 3
Update 2:
Nope, that doesn't seem to do the trick. I seemingly was just "lucky" one time.
Still get the issue.
Doubt it is the health check, as the old containers are listed by portainer as "completed" instead of "failed" and it isn't responding to the changed interval and timeout.
Ornias1993
on 14 May 2020
What OS is your host?
Roxedus
on 14 May 2020
Deb. 10
No offense intended, but how should that make the docker container shut itself down? ;)
edit
It looks like the container itself issues an internal shutdown... It doesn't look like there is anything docker (and thus the host) can do about it.
Ornias1993
on 14 May 2020
Im just trying to gather as much information as I can.
And it does seem like it starts the shutdown process while executing the init scripts.
Could you add S6_BEHAVIOUR_IF_STAGE2_FAILS=2 as a env? Wondering if there is some verbosity getting lost.
Roxedus
on 14 May 2020
@Roxedus No problem :)
I've added the env, if it happens again i'll post it.
(it doesn't always happen it seems, about 1 in 30 restarts it installs fine)
Ornias1993
on 14 May 2020
👍 What that should do is actually shutdown the container on a error in the start up, rather than when one of the services fail (which shouldn't even be started) at this stage.
Roxedus
on 14 May 2020
And it hit the snag again:
Ornias1993
on 14 May 2020
Interesting, this time it actually seems to finish... but still shut down....
Not more verbose though.
Ornias1993
on 14 May 2020
Hmm. Although we both agree its not the health check, can you remove it, just so its out of the mix.
healthcheck:
disable: true
Nice thing about docker: Done and updated the service.
Ornias1993
on 14 May 2020
Well, this is interesting...
First container it spun up is now stuck at this for a few minutes:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
-------------------------------------
GID/UID
-------------------------------------
User uid: 4242
User gid: 4242
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-install: executing...
-----------------------
| Updating Organizr |
-----------------------
There is a lot of load atm, so it could take some time.
Still strange that it isn't more verbose... You sure there isn't a flag to turn it more verbose?
Ornias1993
on 14 May 2020
The install process is very verbose. At that stage it is running a series of git processes, which all outputs to stdout.
https://github.com/Organizr/docker-organizr-v2/blob/master/root/etc/cont-init.d/30-install#L16-L22
Roxedus
on 14 May 2020
Good point, it seems it only outputs stdout to dockerlog at certain times...
Anyhow, it ook a while (like 10 minutes), but this time it ran fine...
It shouldn't and this is the only container having this issue. I'll try looking into the network speed in docker containers (maybe something is wrong there), but still: even with a VERY low network speed, that shouldn't utterly prevent this docker container for being ran.
Any idea why organizr isn't just part of the docker container with a github action to push a new container every version?
organizr docker log 14-05-2020 16-53.txt
Ornias1993
on 14 May 2020
Slow internet is now supposed to stop the container from working.
The way Organizr currently stores data stops us from having a proper release workflow. That's up to @causefx to change.
You can try Organizr/docker-organizr to eliminate the fact that the current image has somewhat outdated packages.
Roxedus
on 14 May 2020
now?
What part of the datascheme is stopping you?
Whats the different between the official docker and Organizr/docker-organizr ?
Ornias1993
on 14 May 2020
ahh shoot, I see now... Thats the repo the dockerhub container is based on right?
Ornias1993
on 14 May 2020
User images get stored with the application files.
As for support there is no difference between orgtools and organizr images. We just havent made the switch yet.
Roxedus
on 14 May 2020
Related issues
roblandry
·
5Comments
CBers
·
4Comments
Ryonez
·
6Comments
STaRDoGG
·
4Comments
Cookie-Monster-Coder
·
5Comments
Most helpful comment
Ah, yeah, that makes sense. Sorry guys, working with contractors at the house at the moment.