docker container 3.4.1+ - configuration updates

[schories]

What is your set up?

Self Hosted Docker

Version

3.4.1

Describe the issue

In short:

• supporting/paying (full plugin set, don't remember the exact fancy name) self-hosting customer
• software itself is really nice, when it works
• however, docker image releases are poorly managed: at least every 3-6 months serious issues with docker images: changes are not communicated upfront, instead one has to always spend time comparing changelog and config files, hunting for clues as well as digging through log files

This is disappointing.

Marcel: Instead of lowering prices, can we increase release quality, please? Kindly let me know how to achieve that. I'd like to help. Here are my humble suggestions:

• notification / email newsletter for UPCOMING config changes
• config checker tool/script/or similar

I understand

• your focus on SaaS,
• non-supporting users can't expect anything
• even supporting users only pay a fraction of the true cost to run your company

But therefore please either officially discontinue or mark the docker images as non-supported / non-production or let us find a better way for the supporting users.

Reproduction steps

Install 3.4.1 or later and have it crashing even before the login page.

Error Logs (LEANTIMEFOLDER/storage/logs)

Won't invest time into this often anymore, sorry.

[marcelfolaron]

Thanks for reaching out and for your patience. I understand your concern and appreciate your candor.

You're absolutely right that we need to do better with communicating changes, especially ones that impact self-hosting configurations.

The recent changes to the docker image were implemented to address long standing security concerns (running leantime as root) and to follow best practices so that docker based installs can be compatible with reverse proxies, container management tools like podman, portainer, cloudron etc and work well with OIDC solutions. Many of the previous issues in the docker build process were fixed but unfortunately that meant some of the configurations had to change as well.

All of this is to say that Docker is a high priority for us and these recent changes are meant to stabilize the image as we move forward.

We had added a Common Issues section to the docker readme but that was clearly not enough and I'll work on more proactive outreach options.

Your suggestions are excellent, and I will take a look at building a config checker to verify compatibility.

Would you be willing to share more details about your specific setup?

Again, thank you for your patience and for pushing us to do better.

[gloriafolaron]

Just wanting to chime in here and say thank you for the feedback.

One thing I think we haven't had a good solution for is the variations in setups. Docker tends to be more consistent in how folks use it but we do occasionally see outliers.

Marcel, I'm wondering if we can also do a better job about outlining the minimum setups that we support. I can see this on the dev docs and on website FAQ.

I know we have reqs to run but there may be more we can do to outline tested procedures / setups while we're at it.

Thanks again for the feedback.

[schories]

Thank you for your fast & kind feedback @gloriafolaron @marcelfolaron ! I'll have time to test during the weekend and will reply with hopefully more useful information then.

[marcelfolaron]

Thanks. A few pointers as you head into the weekend:

1. Our current docker compose file is the best starting point as it has been tested with various platforms https://github.com/Leantime/docker-leantime/blob/master/docker-compose.yml

2. The internal port has changed to 8080. Make sure that your current compose file maps the external port to that one internally.

3. You can still run Leantime as root user and that is the default. If you want to run Leantime as anything else you have to add -PUID=
   PGID=
   into the env vars or env file.

4. Volume file permissions: When changing from root to non root user (or if the user has changed) the file permissions on the volumes created previously will be off. To fix that just run:

   docker exec -it leantime chown -R www-data:www-data /var/www/html/userfiles \ 
                                      /var/www/html/public/userfiles \ 
                                      /var/www/html/storage/logs \ 
                                      /var/www/html/app/Plugins
   docker exec -it leantime chmod -R 775 /var/www/html/userfiles \ 
                                      /var/www/html/public/userfiles \ 
                                      /var/www/html/storage/logs \ 
                                      /var/www/html/app/Plugins
   
   

https://github.com/Leantime/docker-leantime?tab=readme-ov-file#docker-specific-configuration-options