-
Notifications
You must be signed in to change notification settings - Fork 473
How to force a rebuild of the namespaces/repositories list? #1870
Comments
I think that the problem is not the missing data. Further checks revealed that data is in the DB (tags, namespaces, ...) and that the UI behaved errant: couldn't log out, couldn't check the list of issued application tokens, ... The browser's console spits out an error on missing jQuery.
Could it be related to https://github.com/SUSE/Portus/pull/1811/files ? Any workaround you can think of in the meantime? Thanks! |
The docker images [0] are not being built for a while and it's possible that we got a broken image for You could try |
Thanks for the feedback @vitoravelino. Will try to build it by myself. Wouldn't I succeed, is downgrade supported or at least expected to work? |
Well, it's supposed to work. If something is not working, we should fix it and release a new patch version. Let us know. |
I have built a Docker image from this repository's I updated my
Any extra step should I run? |
By downgrading to
Any migration step to run apart from |
What I've done in the past was copying docker[-compose] files to the root folder and running |
About the vulnerabilities error, I recommend you to restart everything. That error should not happen because this attribute is available for both Also, be aware that if you've downgraded to |
I think I'd need some guidance on getting the image built. The image I build from I'm not a SUSE guy, so I barely understand that the Tried Any help would be appreciated :) |
Can anyone give me some pointers to build a Docker image for |
I started over with Thanks! |
I have
portus:head
running with docker compose and after pulling a new version of the image, runningrake db:migrate
and restarting, I have no namespaces nor repositories available in the UI. I expected to have them back available by forcing the background service to run withstrategy: update-delete
, but nothing appeared.Is there some command to be run to force such syncing that I may have missed? Is this a bug instead?
Thanks!
The text was updated successfully, but these errors were encountered: