Synology Diskstation Docker Install about grocy-docker

[gkron92]

I installed via docket. All good

…

Sent from my iPhone

On Mar 31, 2020, at 2:15 PM, James Addison ***@***.***> wrote:  @gkron92 Although that's not ideal, it sounds like you found a workaround. Unfortunately I don't have access to Synology, and I'm unsure we can easily test or reproduce the problem. If anyone's able to provide repro steps that don't require Synology -- or know of another way to further investigate the issue here, we can look into it further. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[berrnd]

I've moved this to grocy/grocy-docker...

[Rayregula]

@gkron92 I'm not using docker through synology but have been having trouble figuring out how to get grocy working through docker for the last few days and have seen the same error on the nginx version that you mentioned. as for the normal grocy/grocy-docker:grocy version I think my issue may have something to do with it not building correctly as in the readme is says to use "docker-compose pull # if you haven't pulled or built" however for me docker says that "docker-compose" is not a recognized command and I feel like I've run out of things to try. Also haven't been able to get anything showing in volume I created for it (assuming I did it right) using "-v /home/docker/grocy:/config"

Jason

[gkron92]

I actually switched to Hass.io using this package.

https://community.home-assistant.io/t/hass-io-on-synology-dsm-native-package/125559/23

And then installed grocy using this. Not ideal but up and running. The docker install should be fixed or made a lot easier.

https://community.home-assistant.io/t/community-hass-io-add-on-grocy/112422

[Rayregula]

I'll take a look at it when I get a chance, thanks.

[HydrelioxGitHub]

I've the same issue. ERR_CONNECTION_REFUSED after running the container.

[jayaddison]

@gkron92 Although that's not ideal, it sounds like you found a workaround. Unfortunately I don't have access to Synology, and I'm unsure we can easily test or reproduce the problem.

If anyone's able to provide repro steps that don't require Synology -- or know of another way to further investigate the issue here, we can look into it further.