Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Team,
I to be honest I have gotten lazy in the last couple of years and I leverage the ContainerStation GUI now 99% of the time. I love your work because I've been on Qnaps since 2006 and PushOver since 2016. That said if I just use the run command the docker dies on a reboot or container station restart. I can't use the GUI to create the container because I can't build and exposed share for and the script needs access to:
So I started playing with the compose instructions but I think there needs to be more in the readme for those that are not versed in or have forgotten (my case) everything they knew about compose :-)
So if put your compose tex in a docker-compose.yml file and run docker-compose create it builds but when I try to start it freaks because (I believe) there is no network defined in the compose file.
It would be a fantastic contribution (I'm willing to help test or whatever I can) if you can help everyone come up with a clean way of making the docker run permanently on ContainerStation.
Thanks again for the great work!