[GH-ISSUE #432] docker errot #263

New issue

Open

opened 2026-02-27 15:58:01 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 15:58:01 +03:00

Owner

Originally created by @tree1123 on GitHub (Apr 25, 2021).
Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/432

when setup use docker in centos8.2
i follow this
https://github.com/retspen/webvirtcloud/wiki/Docker-Installation-&-Update

STEP 10 error

STEP 10: RUN python3 -m venv venv && . venv/bin/activate && pip3 install -U pip && pip3 install wheel && pip3 install -r conf/requirements.txt && chown -R www-data:www-data /srv/webvirtcloud
/bin/sh: 1: pip3: not found
Error: error building at STEP "RUN python3 -m venv venv && . venv/bin/activate && pip3 install -U pip && pip3 install wheel && pip3 install -r conf/requirements.txt && chown -R www-data:www-data /srv/webvirtcloud": error while running runtime: exit status 127

and i try it every step
when enter chown -R www-data:www-data /srv/webvirtcloud

chown: 无效的用户: “www-data:www-data”

Originally created by @tree1123 on GitHub (Apr 25, 2021). Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/432 when setup use docker in centos8.2 i follow this https://github.com/retspen/webvirtcloud/wiki/Docker-Installation-&-Update STEP 10 error STEP 10: RUN python3 -m venv venv && . venv/bin/activate && pip3 install -U pip && pip3 install wheel && pip3 install -r conf/requirements.txt && chown -R www-data:www-data /srv/webvirtcloud /bin/sh: 1: pip3: not found Error: error building at STEP "RUN python3 -m venv venv && . venv/bin/activate && pip3 install -U pip && pip3 install wheel && pip3 install -r conf/requirements.txt && chown -R www-data:www-data /srv/webvirtcloud": error while running runtime: exit status 127 and i try it every step when enter chown -R www-data:www-data /srv/webvirtcloud chown: 无效的用户: “www-data:www-data”

kerem commented

2026-02-27 15:58:01 +03:00

Author

Owner

@catborise commented on GitHub (Apr 25, 2021):

there is not any problem with that dockerfile.
i try it now on oel 8.3(same with centos 8) without any problem it works as expected with podman(clone of docker)
manuel install also works for now(fixed)

@catborise commented on GitHub (Apr 25, 2021): there is not any problem with that dockerfile. i try it now on oel 8.3(same with centos 8) without any problem it works as expected with podman(clone of docker) manuel install also works for now(fixed)

kerem commented

2026-02-27 15:58:01 +03:00

Author

Owner

@ssbaksa commented on GitHub (Apr 26, 2021):

If I may add something to this.
We have talked abut this upgrade stuff (Problem with update while using Docker #380) and I have decided against upgrade. I am building new docker and just scp database from old image to my backup storage and back into new one. It is simple and it works and as catborise said, it is more on container way of doing things. I just keep some old images for security sake (if I mess something badly).

I hope that this helps.

@ssbaksa commented on GitHub (Apr 26, 2021): If I may add something to this. We have talked abut this upgrade stuff (Problem with update while using Docker #380) and I have decided against upgrade. I am building new docker and just scp database from old image to my backup storage and back into new one. It is simple and it works and as catborise said, it is more on container way of doing things. I just keep some old images for security sake (if I mess something badly). I hope that this helps.

kerem commented

2026-02-27 15:58:01 +03:00

Author

Owner

@catborise commented on GitHub (Apr 26, 2021):

@ssbaksa there is a more convenient way of creating new container without copying dbfile.
“Docker volumes” it can keep dbfile. whenever you create a new docker you can mount it.
browse: https://docs.docker.com/storage/volumes/

@catborise commented on GitHub (Apr 26, 2021): @ssbaksa there is a more convenient way of creating new container without copying dbfile. “Docker volumes” it can keep dbfile. whenever you create a new docker you can mount it. browse: https://docs.docker.com/storage/volumes/

kerem commented

2026-02-27 15:58:01 +03:00

Author

Owner

@ssbaksa commented on GitHub (Apr 26, 2021):

Oh, I know that. We have been talked about it but I was to lazy to
implement it, but thanks for reminder.

On Mon, 26 Apr 2021, 11:40 catborise, @.***> wrote:

@ssbaksa https://github.com/ssbaksa there is a more convenient way of
creating new container without copying dbfile.
“Docker volumes” it can keep dbfile. whenever you create a new docker you
can mount it.
browse: https://docs.docker.com/storage/volumes/

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/retspen/webvirtcloud/issues/432#issuecomment-826681809,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEYIXMFUACHCZC3XHEGMSETTKUYH5ANCNFSM43QZROMA
.

@ssbaksa commented on GitHub (Apr 26, 2021): Oh, I know that. We have been talked about it but I was to lazy to implement it, but thanks for reminder. On Mon, 26 Apr 2021, 11:40 catborise, ***@***.***> wrote: > @ssbaksa <https://github.com/ssbaksa> there is a more convenient way of > creating new container without copying dbfile. > “Docker volumes” it can keep dbfile. whenever you create a new docker you > can mount it. > browse: https://docs.docker.com/storage/volumes/ > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/retspen/webvirtcloud/issues/432#issuecomment-826681809>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEYIXMFUACHCZC3XHEGMSETTKUYH5ANCNFSM43QZROMA> > . >