-
Notifications
You must be signed in to change notification settings - Fork 475
lib/tasks/portus.rake#L50 uninialized namespace #1036
Comments
This would be the expected behavior if there was no registry configured. Are you sure your registry is configured properly? |
Another possibility is that the user to be created was supposed to have a private namespace that clashed with an existing one. @EugenMayer maybe this is your case ? If so, we could extend that rake task to be more informative about this case. |
@mssola it happens during initial bootstrap of a fresh portus using my test-repo https://github.com/EugenMayer/docker-image-portus/tree/master/test - if there is a namespace conflict, i am not sure "how" - its probably related to the entrypoint script https://github.com/EugenMayer/docker-image-portus/blob/master/build/startup.sh#L43 |
Then it's exactly what @monstermunchkin said, you have to create the registry in the DB before creating users. From your From our side, maybe we can improve this by adding a check for the existence of a registry before doing anything at all. And it would also be nice from our side to provide a rake task for creating a new registry (I see that you have one of your own right ?) |
Moreover, the portus:create_user taks has now a check preventing to create users if there is no registry. Fixes SUSE#1036 Signed-off-by: Miquel Sabaté Solà <msabate@suse.com>
looks like either namespace is not initialized yet or probably in some cases
https://github.com/SUSE/Portus/blob/master/lib/tasks/portus.rake#L50
u.namespace.name
The text was updated successfully, but these errors were encountered: