I would love to be able to spin up a container for this cocktail recipe thing I found on Docker Hub.
https://hub.docker.com/r/gthole/drink-stash
I am running a Synology DSM 7.2, I have Portainer and have enough knowledge to set up basic things with lots of guides like plex/pihole. But since this is such a niche app my lack of knowledge is hurting.
Anyone have guidance for setting this up for someone with my tools and experience?
Lol, the snippet has a mistake. The environment section should look like one of the 2 ways shown there: https://docs.docker.com/compose/compose-file/compose-file-v3/#environment
So either
environment: - SECRET_KEY= - ALLOWED_HOSTS=Or
environment: SECRET_KEY: ALLOWED_HOSTS:Well, with “- SECRET_KEY=” I at least got a different error, a bind mount fail?
I see what’s the problem this time, in your case you should probably use named volumes instead of bind-mount (which us what it is trying to do). I’m going to sleep now but if you can’t figure it out I can send an example tommorow.
Not sure on the terms, but I did change the volume lines to direct to folders I pre-made in /volume1/drink-stash/data (same for public)
Try this:
version: '3.7' services: api: image: 'gthole/drink-stash:latest' init: true restart: 'always' environment: - SECRET_KEY=YOUR_SECRET_KEY - ALLOWED_HOSTS=SYNOLOGY_HOSTNAME_OR_IP ports: - 8081:8000 volumes: - drink-stash-data:/data - drink-stash-public:/public volumes: drink-stash-data: drink-stash-public:This will create volumes instead of mounting the folders. Mounting the folders (which is what you tried doing before) should be possible and nicer to use since you would be able to navigate the files directly, but since I do not know the filesystem and layout of synology it’s harder for me to help there. Using named volumes like I just sent you should work for any filesystem/layout so you shouldnt have any problem with that.
Also, use the synology hostname and/or ip for the allowed_hosts, localhost would only work if you were running that on your computer. The app should then be available at http://SYNOLOGY_HOSTNAME_OR_IP:8081
Well that did allow the Portainer to compile without error and deploy so I really appreciate the help! When navigating to the http://(my ip):8081 though I get a white page with “Bad Request (400)” on it
Hard to say, any logs?
Hmm, no errors popped up and the container is running. In the Container Manager details it shows the port 8081, so not sure…I’ll try to troubleshoot some more, but I really appreciate you taking the time!
Finally got it to work! Thanks for your help, I took another stab at it after a few weeks of learning other things and it clicked