January 12Jan 12 For anyone coming here for support, this Mealie Unraid application template is out of date and does not accurately reflect the correct environment variables listed on the Mealie documentation. https://docs.mealie.io/documentation/getting-started/installation/backend-config/#emailWhile it still may work, I would recommend you review and update the template when you install it with the correct variables.It seems the owner of this CA application @CatDuck is no longer active and is not updating the template.
January 13Jan 13 11 hours ago, mswdev said:For anyone coming here for support, this Mealie Unraid application template is out of date and does not accurately reflect the correct environment variables listed on the Mealie documentation. https://docs.mealie.io/documentation/getting-started/installation/backend-config/#emailWhile it still may work, I would recommend you review and update the template when you install it with the correct variables.It seems the owner of this CA application @CatDuck is no longer active and is not updating the template.Specifically, what did you find @mswdev? I've noticed the obvious LDAP section that is missing. What did you see?
January 13Jan 13 7 hours ago, frank_sp61 said:Specifically, what did you find @mswdev? I've noticed the obvious LDAP section that is missing. What did you see?The SMTP variables are outdated where one of them is incorrect causing SMTP to not work. It's missing a LOT of other docker variables like the OpenAI integrations, etc.
January 14Jan 14 With that in mind, how can I modify the template without breaking my current deployment. I'd like to be able to test a template without interfering with my current production docker container. Thanks! Also, I've looked into the logs and it shows these variables. Is this from the application or the template? "LDAP_AUTH_ENABLED": false, "LDAP_SERVER_URL": null, "LDAP_TLS_INSECURE": false, "LDAP_TLS_CACERTFILE": null, "LDAP_ENABLE_STARTTLS": false, "LDAP_BASE_DN": null, "LDAP_QUERY_BIND": null, "LDAP_QUERY_PASSWORD": null, "LDAP_USER_FILTER": null, "LDAP_ADMIN_FILTER": null, "LDAP_ID_ATTRIBUTE": "uid", "LDAP_MAIL_ATTRIBUTE": "mail", "LDAP_NAME_ATTRIBUTE": "name", Edited January 14Jan 14 by frank_sp61
January 31Jan 31 On 1/14/2026 at 3:43 AM, frank_sp61 said:With that in mind, how can I modify the template without breaking my current deployment. I'd like to be able to test a template without interfering with my current production docker container. Thanks! Also, I've looked into the logs and it shows these variables. Is this from the application or the template? "LDAP_AUTH_ENABLED": false, "LDAP_SERVER_URL": null, "LDAP_TLS_INSECURE": false, "LDAP_TLS_CACERTFILE": null, "LDAP_ENABLE_STARTTLS": false, "LDAP_BASE_DN": null, "LDAP_QUERY_BIND": null, "LDAP_QUERY_PASSWORD": null, "LDAP_USER_FILTER": null, "LDAP_ADMIN_FILTER": null, "LDAP_ID_ATTRIBUTE": "uid", "LDAP_MAIL_ATTRIBUTE": "mail", "LDAP_NAME_ATTRIBUTE": "name",You can simply edit/update the container template and at the bottom of all the configuration options you can manually add more path, ports, variables, labels, devices, etc. via the "Add another Path, Port, Variable, Lavel or Device" button. Using that you can add the missing or additional docker variables you'd like to use from the Mealie documenation.
April 15Apr 15 I've recently installed this docker container and also noticed it was still on the nightly tag. Can I easily change it to latest now? Edited April 15Apr 15 by mikescott typo
April 16Apr 16 17 hours ago, mikescott said:I've recently installed this docker container and also noticed it was still on the nightly tag. Can I easily change it to latest now?I changed to latest awhile back. For some reason I had to backup and download recipe database from mealie. I had to remove the docker fully and then reinstall and remove ":nightly" from the template. Then restore from backup file. Not sure why I couldn't just drop the ":nightly" but you could try this way first.
April 18Apr 18 On 4/16/2026 at 5:52 AM, Gragorg said:I changed to latest awhile back. For some reason I had to backup and download recipe database from mealie. I had to remove the docker fully and then reinstall and remove ":nightly" from the template. Then restore from backup file. Not sure why I couldn't just drop the ":nightly" but you could try this way first.I wonder if it is because the nightly you were on was newer than the latest. That is, maybe switching to latest actually downgraded you. I'm thinking to wait when latest surpasses the nightly, but I'm not sure where the best place to check the versions getting pushed under each tag for the official mealie would be. This way the tag change will be like a normal update....not sure if this is correct line of thinking.When you say backup and download the recipe database; are you referring to some internal Mealie backup feature, or a postgreSQL backup? Edited April 18Apr 18 by mikescott additional note
April 18Apr 18 13 hours ago, mikescott said:I wonder if it is because the nightly you were on was newer than the latest. That is, maybe switching to latest actually downgraded you.I'm thinking to wait when latest surpasses the nightly, but I'm not sure where the best place to check the versions getting pushed under each tag for the official mealie would be. This way the tag change will be like a normal update....not sure if this is correct line of thinking.When you say backup and download the recipe database; are you referring to some internal Mealie backup feature, or a postgreSQL backup?Yes use the internal mealie backup. Go to Settings---Admin Settings---Backups (This will appear on the side bar on top left side). Create backup and download. This is the same screen to restore the backup also.I tried to wait for a long time till the versions lined up but it never happened. As long as you have the recipe backup file you should be good. Did you try just removing the ":nightly" from the repository?
April 18Apr 18 48 minutes ago, Gragorg said:Yes use the internal mealie backup. Go to Settings---Admin Settings---Backups (This will appear on the side bar on top left side). Create backup and download. This is the same screen to restore the backup also.I tried to wait for a long time till the versions lined up but it never happened. As long as you have the recipe backup file you should be good. Did you try just removing the ":nightly" from the repository?Thank you for the reply and information! I did the backup and download, but then went digging into the tags, and I think I got lucky! I intentionally haven't updated my nightly instance in about a week, and I saw this below (as of today Apr 18, 2026). The latest tag was pushed to 3.16.0 and was published very recently; meaning the latest tag is now newer than my non-updated nightly package.I was able to simply stop the container > change tag to latest > spun up again successfully....doing this it was like updating the image. I think the issue exists if your nightly is newer than the latest
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.