Ha, here comes the problem. with the installation of COPR cluster via command: "docker-compose up", everything looks good, and I can upload srpm and build my version of rpm package successfully, but there is one issue that when browsing git-dist http pages(http://git-dist-http-hostname:port/cgit), it always display "No repositories found" which is incorrect, maybe there is some configuration issue in compose yaml?
On Thu, Sep 1, 2022 at 9:24 AM TommyLike Hu <[email protected]> wrote: > Thanks, The cluster works well in the way docker composing, Now I am > learning COPR, I also would like to have a try if this PR gets merged and > introduce a kubernetes version. > > On Wed, Aug 31, 2022 at 4:22 AM Jakub Kadlcik <[email protected]> wrote: > >> Hello, >> I hope you found the blog post helpful. >> >> There is also an open pull request allowing to run Copr in OpenShift >> https://pagure.io/copr/copr/pull-request/2193 >> >> It isn't finished yet (documentation, etc) but it should work. >> >> Jakub >> >> On Thu, Aug 25, 2022 at 1:18 PM TommyLike Hu <[email protected]> >> wrote: >> > >> > Thanks, that's incredible! I will follow your guidance and have a try :) >> > >> > On Thu, Aug 25, 2022 at 6:40 PM Sérgio Basto <[email protected]> wrote: >> >> >> >> On Thu, 2022-08-25 at 15:47 +0800, TommyLike Hu wrote: >> >> >> >> Hey COPR team, >> >> Is there any document on how to run a COPR server on the kubernetes >> cluster? Including the builder if it's possible. >> >> >> >> >> >> You have >> http://frostyx.cz/posts/copr-docker-compose-without-supervisord and >> previous article https://frostyx.cz/posts/copr-stack-dockerized >> >> >> >> here is my notes when I build my copr builder (based on previous >> article mention here): >> >> >> >> dnf install docker docker-compose podman >> >> /usr/sbin/usermod -a -G docker sergiomb >> >> cat /etc/group | grep sergiomb >> >> systemctl start docker >> >> >> >> user: >> >> git clone https://pagure.io/copr/copr.git >> >> cd copr/ >> >> docker-compose up -d >> >> >> >> >> >> after we need init database and add create the chroots >> >> docker exec -it copr_frontend_1 bash >> >> cat /usr/bin/init-database.sh >> >> #!/bin/bash >> >> >> >> cd /usr/share/copr/coprs_frontend/ && copr-frontend create-db >> --alembic alembic.ini >> >> copr-frontend create-chroot >> >> $(ls /etc/mock/{fedora--{i386,x86_64}.cfg,epel--x86_64.cfg} |xargs >> -I{} -n1 basename {} .cfg) >> >> >> >> and the problems start here >> >> the components of corp use corp rpms on >> https://copr.fedorainfracloud.org/coprs/g/copr/copr/ and not the git >> source , so the fix on git aren't there >> >> >> >> @copr/copr Copr >> >> we need this commit >> https://pagure.io/copr/copr/c/0e1e9b20ad5d2a72e6368e353078cca0bea75dab?branch=main >> to init db >> >> >> >> Commit - copr/copr - 0e1e9b20ad5d2a72e6368e353078cca0bea75dab - >> Pagure.io >> >> copr / copr Clone Source Code GIT Documentation GIT Learn more about >> these different git repos. >> >> and we need this commit >> https://pagure.io/copr/copr/c/15726fc653461d8e0309602b70c4ad23984c0fff?branch=main >> to builder sign the packages (this one is docker configuration should be >> transparent) >> >> >> >> Commit - copr/copr - 15726fc653461d8e0309602b70c4ad23984c0fff - >> Pagure.io >> >> copr / copr Clone Source Code GIT Documentation GIT Learn more about >> these different git repos. >> >> copr-frontend create-chroot also have issues that I solved manually >> directly on database , after talk with copr guys , and is running smooth >> >> >> >> _______________________________________________ >> >> copr-devel mailing list -- [email protected] >> >> To unsubscribe send an email to >> [email protected] >> >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> >> List Guidelines: >> https://fedoraproject.org/wiki/Mailing_list_guidelines >> >> List Archives: >> https://lists.fedorahosted.org/archives/list/[email protected] >> >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue >> >> >> >> >> >> -- >> >> >> >> Sérgio M. B. >> >> >> >> _______________________________________________ >> >> copr-devel mailing list -- [email protected] >> >> To unsubscribe send an email to >> [email protected] >> >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> >> List Guidelines: >> https://fedoraproject.org/wiki/Mailing_list_guidelines >> >> List Archives: >> https://lists.fedorahosted.org/archives/list/[email protected] >> >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue >> > >> > _______________________________________________ >> > copr-devel mailing list -- [email protected] >> > To unsubscribe send an email to [email protected] >> > Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> > List Archives: >> https://lists.fedorahosted.org/archives/list/[email protected] >> > Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue >> _______________________________________________ >> copr-devel mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedorahosted.org/archives/list/[email protected] >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue >> >
_______________________________________________ copr-devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
