docker compose error about sregistry HOT 7 CLOSED

#405 was merged, we should be able to close this issue.

from sregistry.

We probably just need to update the compose file for the current version! It looks like all of the current top level images should be moved under services, with possibly a version too,eg.,https://docs.docker.com/compose/compose-file/

If you want to try that I can make suggestions, and when we stumble on something working can do a PR!

from sregistry.

I'm not an expert of docker compose...
if you can update the installation files etc etc
I would be more than happy to test the new installation procedure.

from sregistry.

you don't need to be an expert! It's literally just yaml, and one level of nesting. Here is the example they have:

The only missing piece for the files here is the top level "services" to wrap what we already have.

from sregistry.

As suggested, I was able to install sregistry just modifying the docker-compose.yaml file by placing everything under the "services:" top level tag.

from sregistry.

woohoo! If you'd like to pull request with these changes (in the root docker-compose.yaml and the one in the https folder) it would be hugely appreciated. If not, I can make the same changes and ask for a quick review.

And see - you totally rocked it!

from sregistry.

This will be closed by #405 where I've updated instructions (docs) and the docker-compse.yml recipes.

from sregistry.