The admin/superuser is not able to remove a collection owned by a regular user

I’ve deployed an sregistry instance and created two users.

1. The first user has been created by logging in the sregistry instance using the github authentication. After the user has been created, I’ve set the permissions for this user to admin and superuser using manage.py add_admin and manage.py add_superuser. On the Django administration site I can see that everything looks good.
2. The second user I created from the Django administration site. It’s not an account to be used by a real user, there is no github account associated. This account is used by a Continuous Integration pipeline. Only the access token will be used to push singularity images to the sregistry instance.

A collection is automatically created when an image is pushed from the CI/CD pipeline. However, I noticed that the superuser/admin is not able to remove/modify a collection owned by this user.

Is this the intended behaviour, or is this a bug? Possibly related: Would you suggest this setup when there is a need for pushing images from a CI/CD pipeline that is not associated with a real user?

How would you suggest to modify (and remove) a collection, maybe from a shell in the docker instance running sregistry?

[vsoch]

Awesome! I’ll merge, and you can update your branch with master, or wait (a little longer) for the automated build. Thanks again!

[RonaldEnsing]

I can confirm that #230 solves it.