glidekirkland

Just reran the setup, your changes fixed it! No errors when setting chmod permission to 0775 Thanks for getting it to work. Can you push that image to latest? Thank a lot!

What's the name of the new image?

Ok thanks. I'll try later tonight when I'm back home and will report back!

Ok sounds good - let me know when you have an updated image.

Thanks Taddeus

Further details on how to fix the issue from the docker expert: It’s an issue with the upstream container and an issue with many images in the Docker ecosystem. I’d recommend raising the request upstream to support specifying PUID and PGID. LSIO has a nice write up on why it’s beneficial. https://docs.linuxserver.io/general/understanding-puid-and-pgid

docker is not being run in rootless mode. I asked someone else on the discord im on that manages the cloudbox repo that i'm using, and the guy who is much more of an expert on docker than me says the reason the docker image is having problems is because: "the images don’t support specifying a user/group on the host for file ownership." I'm not sure exactly what this means but I'm sure you have a better idea. Can you make that fix?

Installed separately.

Ubuntu 18.04 LTS on private server with public IP. 4GB RAM, 4 core intel CPU. Created a new user called "seed" separate from root that did all my installations on for obvious security reasons. Server: Docker Engine - Community Engine: Version: 19.03.13 API version: 1.40 (minimum version 1.12) Go version: go1.13.15 Not sure if you need anything else.

I figured it out! Changing the chmod permission from 0775 to 0777 fixes the mariadb issue. But I don't get why the container needs the directories to have 0777 permissions? - name: Create guacamole directories file: "path={{ item }} state=directory mode=0775 owner={{ user.name }} group={{ user.name }} recurse=yes" with_items: - /opt/guacamole - /opt/guacamole/config - name: Reset guacamole directories file: "path={{ item }} state=directory mode=0775 owner={{ user.name }} group={{ user.name }} recurse=yes" with_items: - /opt/guacamole

The new image got rid of the Tini error messages. But still the same issue - for some reason, on restart of a fresh container w/ no changes in configs mariadb just fails to load. Are there error logs for mariadb i can load in more detail that can hep you? Using existing properties file. Using existing MySQL extension. Using existing Duo extension. No permissions changes needed. Database exists. Database upgrade not needed. 2020-11-29 13:30:51,571 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing 2020-11-29 13:30:51,571 INFO Set uid to user 0 succeeded 2020-11-29 13:30:51,572 INFO supervisord started with pid 12 2020-11-29 13:30:52,574 INFO spawned: 'guacd' with pid 15 2020-11-29 13:30:52,576 INFO spawned: 'mariadb' with pid 16 2020-11-29 13:30:52,578 INFO spawned: 'tomcat9' with pid 17 guacd[15]: INFO: Guacamole proxy daemon (guacd) version 1.2.0 started guacd[15]: INFO: Listening on host 0.0.0.0, port 4822 2020-11-29 13:30:52,798 INFO exited: mariadb (exit status 0; not expected) 2020-11-29 13:30:53,799 INFO success: guacd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-11-29 13:30:53,800 INFO spawned: 'mariadb' with pid 273 2020-11-29 13:30:53,800 INFO success: tomcat9 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-11-29 13:30:53,978 INFO exited: mariadb (exit status 0; not expected) 2020-11-29 13:30:55,985 INFO spawned: 'mariadb' with pid 493 2020-11-29 13:30:56,583 INFO exited: mariadb (exit status 0; not expected) 2020-11-29 13:30:59,587 INFO spawned: 'mariadb' with pid 729 2020-11-29 13:30:59,702 INFO exited: mariadb (exit status 0; not expected) 2020-11-29 13:31:00,703 INFO gave up: mariadb entered FATAL state, too many start retries too quickly

the logs basically say mariadb crash/fails to start after reloading the container.

Just to provide some more datapoints, this is the docker logs guacamole output when I do a fresh install using the ansible script: [WARN tini (6)] Tini is not running as PID 1 and isn't registered as a child subreaper. Zombie processes will not be re-parented to Tini, so zombie reaping won't work. To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1. 2020-11-29 12:54:12,512 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing 2020-11-29 12:54:12,513 INFO Set uid to user 0 succeeded 2020-11-29 12:54:12,515 INFO supervisord started with pid 357 2020-11-29 12:54:13,516 INFO spawned: 'guacd' with pid 360 2020-11-29 12:54:13,517 INFO spawned: 'mariadb' with pid 361 2020-11-29 12:54:13,518 INFO spawned: 'tomcat9' with pid 362 guacd[360]: INFO: Guacamole proxy daemon (guacd) version 1.2.0 started guacd[360]: INFO: Listening on host 0.0.0.0, port 4822 2020-11-29 12:54:14,658 INFO success: guacd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-11-29 12:54:14,658 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-11-29 12:54:14,658 INFO success: tomcat9 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Docker logs for guacamole after a restart (no change in configs, i didn't even change the username/password for guacadmin). From here on, no matter if you reboot the ubuntu server or restart it doesn't work. 020-11-29 12:58:18,593 WARN received SIGTERM indicating exit request 2020-11-29 12:58:18,594 INFO waiting for guacd, mariadb, tomcat9 to die 2020-11-29 12:58:18,829 INFO stopped: tomcat9 (exit status 143) 2020-11-29 12:58:18,830 INFO stopped: mariadb (terminated by SIGKILL) 2020-11-29 12:58:18,831 INFO stopped: guacd (terminated by SIGTERM) Using existing properties file. Using existing MySQL extension. No permissions changes needed. Database exists. Database upgrade not needed. [WARN tini (6)] Tini is not running as PID 1 and isn't registered as a child subreaper. Zombie processes will not be re-parented to Tini, so zombie reaping won't work. To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1. 2020-11-29 12:58:20,097 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing 2020-11-29 12:58:20,097 INFO Set uid to user 0 succeeded 2020-11-29 12:58:20,099 INFO supervisord started with pid 10 2020-11-29 12:58:21,101 INFO spawned: 'guacd' with pid 13 2020-11-29 12:58:21,102 INFO spawned: 'mariadb' with pid 14 2020-11-29 12:58:21,103 INFO spawned: 'tomcat9' with pid 15 guacd[13]: INFO: Guacamole proxy daemon (guacd) version 1.2.0 started guacd[13]: INFO: Listening on host 0.0.0.0, port 4822 2020-11-29 12:58:21,436 INFO exited: mariadb (exit status 0; not expected) 2020-11-29 12:58:22,438 INFO success: guacd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-11-29 12:58:22,439 INFO spawned: 'mariadb' with pid 272 2020-11-29 12:58:22,439 INFO success: tomcat9 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-11-29 12:58:22,702 INFO exited: mariadb (exit status 0; not expected) 2020-11-29 12:58:24,704 INFO spawned: 'mariadb' with pid 491 2020-11-29 12:58:25,014 INFO exited: mariadb (exit status 0; not expected) 2020-11-29 12:58:28,019 INFO spawned: 'mariadb' with pid 726 2020-11-29 12:58:28,234 INFO exited: mariadb (exit status 0; not expected) 2020-11-29 12:58:29,235 INFO gave up: mariadb entered FATAL state, too many start retries too quickly

I was editing using nano within my ubuntu server. But actually, you don't even need to edit the config. If you just restart the docker container, or docker stop and docker start the container, it fails to load the second time off of a fresh install throwing those errors about mariadb. FWIW, I'm using this ansible script to deploy your docker image: https://github.com/Cloudbox/Community/blob/master/roles/guacamole/tasks/main.yml I don't understand why it would work on first boot/startup, but when the container is restarted it fails to load forever (start mariadb). The only way to fix is to completely delete the container and config folder, and reinstall upon which it works again on the first boot but fails subsequently. Do you need to set permissions as 0777 on the config folder or something? The ansible script only allows for chmod 0775.

I'm getting a fatal error for the Guacamole image by jasonbean after the docker container is restarted/rebooted: How to replicate issue: 1. Install guacamole (do a fresh install) 2. When guacamole is first launched, it will work (you see the login page) at guacamole.yourdomain.com 3. Restart guacamole docker container (e.g. you've edited the guacamole config or added an extension) 4. Guacamole container will restart successfully, but the mariadb inside the container fails to start. From docker logs --follow guacamole while container is being restarted: [WARN tini (7)] Tini is not running as PID 1 and isn't registered as a child subreaper. Zombie processes will not be re-parented to Tini, so zombie reaping won't work. To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1. 2020-11-28 22:53:15,992 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing 2020-11-28 22:53:15,992 INFO Set uid to user 0 succeeded 2020-11-28 22:53:15,993 INFO supervisord started with pid 11 2020-11-28 22:53:16,995 INFO spawned: 'guacd' with pid 14 2020-11-28 22:53:16,996 INFO spawned: 'mariadb' with pid 15 2020-11-28 22:53:16,997 INFO spawned: 'tomcat9' with pid 16 guacd[14]: INFO: Guacamole proxy daemon (guacd) version 1.2.0 started guacd[14]: INFO: Listening on host 0.0.0.0, port 4822 2020-11-28 22:53:17,365 INFO exited: mariadb (exit status 0; not expected) 2020-11-28 22:53:18,366 INFO success: guacd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-11-28 22:53:18,367 INFO spawned: 'mariadb' with pid 270 2020-11-28 22:53:18,367 INFO success: tomcat9 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2020-11-28 22:53:18,612 INFO exited: mariadb (exit status 0; not expected) 2020-11-28 22:53:20,615 INFO spawned: 'mariadb' with pid 490 2020-11-28 22:53:20,877 INFO exited: mariadb (exit status 0; not expected) 2020-11-28 22:53:23,880 INFO spawned: 'mariadb' with pid 724 2020-11-28 22:53:24,092 INFO exited: mariadb (exit status 0; not expected) 2020-11-28 22:53:25,094 INFO gave up: mariadb entered FATAL state, too many start retries too quickly