Re: Running COPR on kubernetes cluster?
As a follow up, here comes the kustomize yaml for kubernetes.
https://pagure.io/copr/copr/pull-request/2326
On Wed, Aug 31, 2022 at 4:22 AM Jakub Kadlcik 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
> 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 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 -- copr-devel@lists.fedorahosted.org
> >> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> >> 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/copr-devel@lists.fedorahosted.org
> >> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
> >>
> >>
> >> --
> >>
> >> Sérgio M. B.
> >>
> >> ___
> >> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> >> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> >> 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/copr-devel@lists.fedorahosted.org
> >> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
> >
> > ___
> > copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> > Fedora Code of Conduct:
> ht
Re: Inconsistency of bash behaviour on fedora aarch64 and x86_64 images
It's a bug on docker runc component, I upgrade the runc version and everything works well now :） On Tue, Sep 6, 2022 at 10:07 PM TommyLike Hu wrote: > Thanks! Because I tried the folder that should be ok, but still got > unsuccessful, I submitted the bug here [1], but as you said maybe it's not > related to coreutil. > > https://bugzilla.redhat.com/show_bug.cgi?id=2124510 > > > On Tue, Sep 6, 2022 at 9:59 PM Pavel Raiskup wrote: > >> On Tuesday, September 6, 2022 1:38:56 PM CEST TommyLike Hu wrote: >> > I mean this command [1] below doesn't work well on the aarch64 >> container, >> > it's not related to the file/directory permissions at all. >> >> What makes you think so? What is the output from: >> >> $ stat "$directory" >> $ [ -w "$directory" ] ; echo $? >> >> > ``` >> > if [ -w $directory ] ; then echo 'Success!' ; fi >> > ``` >> > Maybe I should report an issue on related package [2] ? >> >> Yes, the binary is owned by coreutils: >> >> $ rpm -qf /usr/bin/\[ >> coreutils-9.0-8.fc36.x86_64 >> >> But '[' is also a Bash built-in. >> >> Pavel >> >> > >> > [1]: https://man7.org/linux/man-pages/man1/test.1.html >> > [2]: https://src.fedoraproject.org/rpms/coreutils >> > >> > On Tue, Sep 6, 2022 at 4:35 PM Pavel Raiskup >> wrote: >> > >> > > On Tuesday, September 6, 2022 1:35:30 AM CEST TommyLike Hu wrote: >> > > > Sure, that would be easy to test this on an arm instance with script >> > > > something like this: >> > > > ``` >> > > > >> > > > if [ -w $directory ] ; then echo 'Success!' ; fi >> > > >> > > What path is held by the $directory / $REPODIR variables? >> > > >> > > Pavel >> > > >> > > P.S. double-quote >> > > >> > > > ``` >> > > > >> > > > On Tue, Sep 6, 2022 at 5:27 AM Jakub Kadlcik >> > > wrote: >> > > > >> > > > > Hello TommyLike, >> > > > > a disclaimer first - I have never tried to run the Copr >> containers on >> > > > > an arm architecture, and I am not really a bash person. But >> > > > > >> > > > > if [ ! -w $REPODIR ] ; then >> > > > > >> > > > > Checks if a file (or I guess a directory) is writable. Are you >> sure >> > > > > you have the correct permissions for $REPODIR ? >> > > > > >> > > > > Jakub >> > > > > >> > > > > On Mon, Sep 5, 2022 at 4:59 PM TommyLike Hu < >> tommylik...@gmail.com> >> > > wrote: >> > > > > > >> > > > > > Hey COPR Developers, >> > > > > > Recently, I am trying to deploy COPR containers on an arm >> > > instance, >> > > > > except for the base image and resalloc pool tag issues, I also >> found >> > > there >> > > > > is a strange thing on bash command, check this code from dist-git >> [1] >> > > below: >> > > > > > ``` >> > > > > > if [ ! -w $REPODIR ] ; then >> > > > > > echo "ERROR: You can not write to $REPODIR" >> > > > > > echo "ERROR: You can not create repos" >> > > > > > exit -1 >> > > > > > fi >> > > > > > ``` >> > > > > > This would always fail in an aarch64 container which uses the >> > > identical >> > > > > dockerfile as the x86 ones. >> > > > > > ``` >> > > > > > >> > > > > > FROM registry.fedoraproject.org/fedora:35 >> > > > > > MAINTAINER copr-devel@lists.fedorahosted.org >> > > > > > >> > > > > > ``` >> > > > > > Could this be a fedora issue? Considering I tried fedora >> 35/36/37 >> > > which >> > > > > all failed. >> > > > > > >> > > > > > >> > > > > > [1]: >> > > > > >> > > >> https://github.com/release-engineering/dist-git/blob/738dc51b8dff6f06a3d4be5f0f480aebf36b1480/scripts/dist-git/setup_git_package#L72 >> > > > > > >> > >
Re: Inconsistency of bash behaviour on fedora aarch64 and x86_64 images
Thanks! Because I tried the folder that should be ok, but still got unsuccessful, I submitted the bug here [1], but as you said maybe it's not related to coreutil. https://bugzilla.redhat.com/show_bug.cgi?id=2124510 On Tue, Sep 6, 2022 at 9:59 PM Pavel Raiskup wrote: > On Tuesday, September 6, 2022 1:38:56 PM CEST TommyLike Hu wrote: > > I mean this command [1] below doesn't work well on the aarch64 container, > > it's not related to the file/directory permissions at all. > > What makes you think so? What is the output from: > > $ stat "$directory" > $ [ -w "$directory" ] ; echo $? > > > ``` > > if [ -w $directory ] ; then echo 'Success!' ; fi > > ``` > > Maybe I should report an issue on related package [2] ? > > Yes, the binary is owned by coreutils: > > $ rpm -qf /usr/bin/\[ > coreutils-9.0-8.fc36.x86_64 > > But '[' is also a Bash built-in. > > Pavel > > > > > [1]: https://man7.org/linux/man-pages/man1/test.1.html > > [2]: https://src.fedoraproject.org/rpms/coreutils > > > > On Tue, Sep 6, 2022 at 4:35 PM Pavel Raiskup > wrote: > > > > > On Tuesday, September 6, 2022 1:35:30 AM CEST TommyLike Hu wrote: > > > > Sure, that would be easy to test this on an arm instance with script > > > > something like this: > > > > ``` > > > > > > > > if [ -w $directory ] ; then echo 'Success!' ; fi > > > > > > What path is held by the $directory / $REPODIR variables? > > > > > > Pavel > > > > > > P.S. double-quote > > > > > > > ``` > > > > > > > > On Tue, Sep 6, 2022 at 5:27 AM Jakub Kadlcik > > > wrote: > > > > > > > > > Hello TommyLike, > > > > > a disclaimer first - I have never tried to run the Copr containers > on > > > > > an arm architecture, and I am not really a bash person. But > > > > > > > > > > if [ ! -w $REPODIR ] ; then > > > > > > > > > > Checks if a file (or I guess a directory) is writable. Are you sure > > > > > you have the correct permissions for $REPODIR ? > > > > > > > > > > Jakub > > > > > > > > > > On Mon, Sep 5, 2022 at 4:59 PM TommyLike Hu > > > > wrote: > > > > > > > > > > > > Hey COPR Developers, > > > > > > Recently, I am trying to deploy COPR containers on an arm > > > instance, > > > > > except for the base image and resalloc pool tag issues, I also > found > > > there > > > > > is a strange thing on bash command, check this code from dist-git > [1] > > > below: > > > > > > ``` > > > > > > if [ ! -w $REPODIR ] ; then > > > > > > echo "ERROR: You can not write to $REPODIR" > > > > > > echo "ERROR: You can not create repos" > > > > > > exit -1 > > > > > > fi > > > > > > ``` > > > > > > This would always fail in an aarch64 container which uses the > > > identical > > > > > dockerfile as the x86 ones. > > > > > > ``` > > > > > > > > > > > > FROM registry.fedoraproject.org/fedora:35 > > > > > > MAINTAINER copr-devel@lists.fedorahosted.org > > > > > > > > > > > > ``` > > > > > > Could this be a fedora issue? Considering I tried fedora 35/36/37 > > > which > > > > > all failed. > > > > > > > > > > > > > > > > > > [1]: > > > > > > > > > https://github.com/release-engineering/dist-git/blob/738dc51b8dff6f06a3d4be5f0f480aebf36b1480/scripts/dist-git/setup_git_package#L72 > > > > > > > > > > > > ___ > > > > > > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > > > > > > To unsubscribe send an email to > > > copr-devel-le...@lists.fedorahosted.org > > > > > > 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/
Re: Inconsistency of bash behaviour on fedora aarch64 and x86_64 images
I mean this command [1] below doesn't work well on the aarch64 container, it's not related to the file/directory permissions at all. ``` if [ -w $directory ] ; then echo 'Success!' ; fi ``` Maybe I should report an issue on related package [2] ? [1]: https://man7.org/linux/man-pages/man1/test.1.html [2]: https://src.fedoraproject.org/rpms/coreutils On Tue, Sep 6, 2022 at 4:35 PM Pavel Raiskup wrote: > On Tuesday, September 6, 2022 1:35:30 AM CEST TommyLike Hu wrote: > > Sure, that would be easy to test this on an arm instance with script > > something like this: > > ``` > > > > if [ -w $directory ] ; then echo 'Success!' ; fi > > What path is held by the $directory / $REPODIR variables? > > Pavel > > P.S. double-quote > > > ``` > > > > On Tue, Sep 6, 2022 at 5:27 AM Jakub Kadlcik > wrote: > > > > > Hello TommyLike, > > > a disclaimer first - I have never tried to run the Copr containers on > > > an arm architecture, and I am not really a bash person. But > > > > > > if [ ! -w $REPODIR ] ; then > > > > > > Checks if a file (or I guess a directory) is writable. Are you sure > > > you have the correct permissions for $REPODIR ? > > > > > > Jakub > > > > > > On Mon, Sep 5, 2022 at 4:59 PM TommyLike Hu > wrote: > > > > > > > > Hey COPR Developers, > > > > Recently, I am trying to deploy COPR containers on an arm > instance, > > > except for the base image and resalloc pool tag issues, I also found > there > > > is a strange thing on bash command, check this code from dist-git [1] > below: > > > > ``` > > > > if [ ! -w $REPODIR ] ; then > > > > echo "ERROR: You can not write to $REPODIR" > > > > echo "ERROR: You can not create repos" > > > > exit -1 > > > > fi > > > > ``` > > > > This would always fail in an aarch64 container which uses the > identical > > > dockerfile as the x86 ones. > > > > ``` > > > > > > > > FROM registry.fedoraproject.org/fedora:35 > > > > MAINTAINER copr-devel@lists.fedorahosted.org > > > > > > > > ``` > > > > Could this be a fedora issue? Considering I tried fedora 35/36/37 > which > > > all failed. > > > > > > > > > > > > [1]: > > > > https://github.com/release-engineering/dist-git/blob/738dc51b8dff6f06a3d4be5f0f480aebf36b1480/scripts/dist-git/setup_git_package#L72 > > > > > > > > ___ > > > > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > > > > To unsubscribe send an email to > copr-devel-le...@lists.fedorahosted.org > > > > 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/copr-devel@lists.fedorahosted.org > > > > Do not reply to spam, report it: > > > https://pagure.io/fedora-infrastructure/new_issue > > > ___ > > > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > > > To unsubscribe send an email to > copr-devel-le...@lists.fedorahosted.org > > > 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/copr-devel@lists.fedorahosted.org > > > Do not reply to spam, report it: > > > https://pagure.io/fedora-infrastructure/new_issue > > > > > > > > > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org 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/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Inconsistency of bash behaviour on fedora aarch64 and x86_64 images
Sure, that would be easy to test this on an arm instance with script something like this: ``` if [ -w $directory ] ; then echo 'Success!' ; fi ``` On Tue, Sep 6, 2022 at 5:27 AM Jakub Kadlcik wrote: > Hello TommyLike, > a disclaimer first - I have never tried to run the Copr containers on > an arm architecture, and I am not really a bash person. But > > if [ ! -w $REPODIR ] ; then > > Checks if a file (or I guess a directory) is writable. Are you sure > you have the correct permissions for $REPODIR ? > > Jakub > > On Mon, Sep 5, 2022 at 4:59 PM TommyLike Hu wrote: > > > > Hey COPR Developers, > > Recently, I am trying to deploy COPR containers on an arm instance, > except for the base image and resalloc pool tag issues, I also found there > is a strange thing on bash command, check this code from dist-git [1] below: > > ``` > > if [ ! -w $REPODIR ] ; then > > echo "ERROR: You can not write to $REPODIR" > > echo "ERROR: You can not create repos" > > exit -1 > > fi > > ``` > > This would always fail in an aarch64 container which uses the identical > dockerfile as the x86 ones. > > ``` > > > > FROM registry.fedoraproject.org/fedora:35 > > MAINTAINER copr-devel@lists.fedorahosted.org > > > > ``` > > Could this be a fedora issue? Considering I tried fedora 35/36/37 which > all failed. > > > > > > [1]: > https://github.com/release-engineering/dist-git/blob/738dc51b8dff6f06a3d4be5f0f480aebf36b1480/scripts/dist-git/setup_git_package#L72 > > > > ___ > > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > > 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/copr-devel@lists.fedorahosted.org > > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > 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/copr-devel@lists.fedorahosted.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org 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/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Inconsistency of bash behaviour on fedora aarch64 and x86_64 images
Hey COPR Developers, Recently, I am trying to deploy COPR containers on an arm instance, except for the base image and resalloc pool tag issues, I also found there is a strange thing on bash command, check this code from dist-git [1] below: ``` if [ ! -w $REPODIR ] ; then echo "ERROR: You can not write to $REPODIR" echo "ERROR: You can not create repos" exit -1 fi ``` This would always fail in an aarch64 container which uses the identical dockerfile as the x86 ones. ``` FROM registry.fedoraproject.org/fedora:35 MAINTAINER copr-devel@lists.fedorahosted.org ``` Could this be a fedora issue? Considering I tried fedora 35/36/37 which all failed. [1]: https://github.com/release-engineering/dist-git/blob/738dc51b8dff6f06a3d4be5f0f480aebf36b1480/scripts/dist-git/setup_git_package#L72 ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org 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/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Running COPR on kubernetes cluster?
Thanks for your tips, I added this change in PR:
https://pagure.io/copr/copr/pull-request/2299 if this could help others.
On Thu, Sep 1, 2022 at 7:59 PM Jakub Kadlcik wrote:
> Hello,
>
> > it always display "No repositories found" which is incorrect
>
> You are right. It can be fixed by editing /etc/cgitrc in the
> copr_distgit-httpd_1 container and adding the following line to the
> end:
>
> scan-path=/var/lib/dist-git/git
>
> Jakub
>
> On Thu, Sep 1, 2022 at 10:32 AM TommyLike Hu
> wrote:
> >
> > 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
> 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
> 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
> 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
> 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
> transp
Re: Running COPR on kubernetes cluster?
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 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 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
>> 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 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 -- copr-devel@lists.fedorahosted.org
>> >> To unsubscribe send an email to
>> copr-devel-le...@lists.fedorahosted.org
>> >> 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/copr-devel@lists.fedorahosted.org
>> >> Do not reply to spam, report it:
>> https://pagure.io/fedora-infrastructure/new_issue
>> >>
>> >
Re: Running COPR on kubernetes cluster?
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 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
> 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 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 -- copr-devel@lists.fedorahosted.org
> >> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> >> 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/copr-devel@lists.fedorahosted.org
> >> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
> >>
> >>
> >> --
> >>
> >> Sérgio M. B.
> >>
> >> ___
> >> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> >> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> >> 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/copr-devel@lists.fedorahosted.org
> >> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
> >
> > ___
> > copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> > To unsubscribe send an email to cop
Re: Running COPR on kubernetes cluster?
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 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 -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> 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/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
>
> --
>
> Sérgio M. B.
>
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> 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/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
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/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Running COPR on kubernetes cluster?
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. ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org 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/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
