Open ohm314 opened 9 months ago
I would try using the version of minio that the registry was developed with - there were breaking changes that I haven't gone to work on anytime recently. I also would suspect there is some issue with EC2 - my suggestion is to get it working locally first then reproduce on EC2 and then you can figure out what EC2 setting might be the issue. I've never tested on RHEL so I'm not sure I can add feedback there, but it's containerized so (I would think) that's not the issue!
Let me know what you think of the above!
also, any reason to not just use a registry that supports pushing SIF (e.g., GitHub packages?) It's expensive to run your own infra (I would know running Singularity Hub for 5 years)!
Well I started off with version you had tagged in the docker-compose - I agree that's what makes most sense. But since that gave me this very same error with the additional warning of mirio being out-of-date, I thought I could maybe go to the latest version and see what happens, but you're right that was probably not the smartest move :) I'll downgrade and try one more time. I may have fixed a few things in my config in the meantime.
I'm looking for a solution where we can maintain a private registry, so I thought it could be worthwhile trying to setup our own. What I am mostly interested in is a registry that will maintain the different containers for different architectures in one place and where I then can easily pull in the right image depending on the arch that I'm running on.
Are you on slack/discord somewhere? I'd love to pick your brains on our use-case if you have some time for a little chat.
OK, so I did retest with the tagged version of minio and I see the same messages in the logs.
Did you test on localhost first (not on EC2)?
I did not :) but getting all the social connect stuff working on my local machine seems like a nightmare.
Hi @vsoch
I've been trying to setup sregistry to test it out and see if it could help for our use-case but I've been struggling to push images onto the registry.
I've followed your documentation configuring and setting everything up (I'm working with the sregistry master branch), but once I try pushing an image I see following error:
This points me to some issue with minio. Looking at the logs in docker compose, i see at startup:
The last messages that match the push requests are:
Looking at the minio trace I see:
Some extra notes:
docker-compose.yaml
file to simply pull the latest image.settings.yaml
,.minio.env
and also the json file that themc
command points me at.surely I'm missing something quite obvious! I'd appreciate your help. Thanks!