You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to upgrade from hawkbit/hawkbit-update-server:0.3.0-mysql to hawkbit/hawkbit-update-server:0.7.0
I can get the container up and running with the new docker-compose-monolith-mysql-with-simple-ui.yml
As our artifacts are larger in size, I had to add the following to the simple-ui environment:
Hi,
this clearly seem to be a problem on the update server. Could you enable some logs there and check what is the issue there?
Do you get the same problem without "previously 0.3.0 populated artifactrepo"? Do you get the same with the clean deployment? Existing of repo shall no be a problem even if the new repo locaton doesn't match the old.
Also, you may try to use the docker compose yaml from the 0.7.0 tag. There could be some incompatibility between docker 0.7.0 images and current master
Hello,
I am trying to upgrade from hawkbit/hawkbit-update-server:0.3.0-mysql to hawkbit/hawkbit-update-server:0.7.0
I can get the container up and running with the new docker-compose-monolith-mysql-with-simple-ui.yml
As our artifacts are larger in size, I had to add the following to the simple-ui environment:
But when attempting to use the perviously 0.3.0 populated artifactrepo, I am unable to upload artifacts.
I get the following error on the simple ui:

As well as the following log output:
Is there a recommend upgrade / migration path or some manual command I might have missed to get this working?
The text was updated successfully, but these errors were encountered: