deploy error

[semrakky]

when i type dokcer-compose up . thanks

[countnazgul]

Stumbled across the same issue. Had to change the repo version to pass this point

• in Dockerfile (in the root folder)
• replaced openSUSE_Leap_15.0 with openSUSE_Leap_15.1 (2 instances)

Once the version has been changed the installation continued

[Jean-Baptiste-Lasselle]

Successfully repaired opensuse/portus:2.5 OCI container image

hi @countnazgul @semrakky replacing openSUSE_Leap_15.0 by openSUSE_Leap_15.1 is not enough, at least if you are using the docker build defined here https://github.com/openSUSE/docker-containers ,published to docker hub with name opensuse/portus:2.5. I read deploy, in the issue title, so I assume you want to deploy, not to build from source. And the images defined in defined here https://github.com/openSUSE/docker-containers are those who should be used for deployment.
Only problem is that https://github.com/openSUSE/docker-containers are buggy, so I found a solution to use, to build a opensuse/portus:2.5 image, all details #2241 (comment)

:)

I will read any feedback from you with interest

[jeanlucmongrain]

users need to understand that Portus as a FoSS is dead. PR are ignored.
this was the last RoR projects I let in my infrastructure.
The market switched to Go for infrastructure applications. Time to switch to https://github.com/goharbor/harbor

[Jean-Baptiste-Lasselle]

users need to understand that Portus as a FoSS is dead. PR are ignored.
this was the last RoR projects I let in my infrastructure.
The market switched to Go for infrastructure applications. Time to switch to https://github.com/goharbor/harbor

hi @bclermont Actually,I worked hard to make portus work reliabily :

• one reason is that I don't want a world where there is only harbor : what happens if they decide, at Harbor, say to change licences, or to make choices that happen to be very harmful to your business model ?
• What do you think ?
• Here is where I stand today : I have an automated deployment that solves all the issues closed, and mot of those still open . I will no doubt, success in the near future, at building portus from source. After digging into it, I am not a big fan of ruby myself, but well, portus really works after the efforts I put into it, and it's fit for production. There is though, one set of feature that portus never considered, it is content trust, notary. I believe I can add without touching a lot of source code.
• What I like about portus, is that it's simple, powerful, and secure enough, to play for rather big development teams.And if it's about distributing signed images to end users, well you have quay and docker hub (anyway you will, publish your app dockerized to docker hub, it's like the containers facebook, every container wants his facebook account).
• If you're customer requires a private hosted docker registry, I believe that setting up a production grade harbor will involve as much work as adding notary integration to Portus, an level up a Portus K8S deployment. Portus is Ruby on Rails, like Gitlab. Gitlab scales in Kubernetes, and so Portus will be able to scale in Kubernetes as well, for sure.
• Where you made me laugh, is that I just tested quickly yesterday another OpenSUSE project, : OBS . Because it is one services they use to package and deliver portus. And it is an opensourec project. It looks like the trendy at SUSE , currently (27000+ commits). Written in Ruby. And guess what, After 10minutes I had corrected 4 errors, for the OBS docker-compose , even though I had git checked out a release tag. Okay, they've got their style at SUSE. Messy. :)
• All in all, whatever the future, I won't regret my work on portus, cause no when I work with harbor, I know exactly what is awesome, what is important, and why. It's a bit like when you switch from debian to centos, you almost don't need to read the docs, the tab key plus --help,and you almost guess everything before finding answers in documentation.

[stale]

Thanks for all your contributions!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.