'latest' tag seems to be broken - docker #2233

New Issue

GiteaMirror · 2025-11-02T04:28:47-06:00

GiteaMirror commented

2025-11-02 04:28:47 -06:00

Originally created by @ToeiRei on GitHub (Aug 22, 2018).

Gitea version (or commit ref): 'latest' docker image as of >1.5
Operating system: photonOS by vmware
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant

Description

docker run --name=Gitea -v gitea-data:/data -p 22:22 -p 3000:3000 --net=DMZ --ip=10.0.0.4 -d gitea/gitea:latest

bails out as follows:

docker: Error response from daemon: chown /var/lib/docker/volumes/gitea-data/_data: invalid argument.
See 'docker run --help'.

while
docker run --name=Gitea -v gitea-data:/data -p 22:22 -p 3000:3000 --net=DMZ --ip=10.0.0.4 -d gitea/gitea:1.5

just works fine.

Details about the image tagged as 1.5:

sha256:cf381b60bc302b6a484b677d547af73f289365a023879a53c5b8ca513b5f0156
Size: 75.4 MB
Created: 2018-07-12 18:13:34
Build on Docker 17.12.0-ce on linux, amd64

gitea-data is a named volume living on a NFS server.

Originally created by @ToeiRei on GitHub (Aug 22, 2018). - Gitea version (or commit ref): 'latest' docker image as of >1.5 - Operating system: photonOS by vmware - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant ## Description `docker run --name=Gitea -v gitea-data:/data -p 22:22 -p 3000:3000 --net=DMZ --ip=10.0.0.4 -d gitea/gitea:latest` bails out as follows: ``` docker: Error response from daemon: chown /var/lib/docker/volumes/gitea-data/_data: invalid argument. See 'docker run --help'. ``` while `docker run --name=Gitea -v gitea-data:/data -p 22:22 -p 3000:3000 --net=DMZ --ip=10.0.0.4 -d gitea/gitea:1.5` just works fine. Details about the image tagged as 1.5: - sha256:cf381b60bc302b6a484b677d547af73f289365a023879a53c5b8ca513b5f0156 - Size: 75.4 MB - Created: 2018-07-12 18:13:34 - Build on Docker 17.12.0-ce on linux, amd64 gitea-data is a named volume living on a NFS server.

GiteaMirror added the issue/stale issue/needs-feedback labels 2025-11-02 04:28:47 -06:00

GiteaMirror closed this issue

2025-11-02 04:28:47 -06:00

GiteaMirror commented

2025-11-02 04:28:48 -06:00

@daviian commented on GitHub (Aug 22, 2018):

How do you mount the nfs volume into the docker container?

@daviian commented on GitHub (Aug 22, 2018): How do you mount the nfs volume into the docker container?

GiteaMirror commented

2025-11-02 04:28:49 -06:00

@ToeiRei commented on GitHub (Aug 22, 2018):

using the local driver:

docker volume create --name gitea-data --driver local --opt type=nfs --opt o=addr=1.2.3.4,rw --opt device=:/path/to/gitea/data/

@ToeiRei commented on GitHub (Aug 22, 2018): using the local driver: `docker volume create --name gitea-data --driver local --opt type=nfs --opt o=addr=1.2.3.4,rw --opt device=:/path/to/gitea/data/`

GiteaMirror commented

2025-11-02 04:28:49 -06:00

@daviian commented on GitHub (Aug 22, 2018):

I think your problem could be somehow related to https://github.com/moby/moby/pull/33695

@daviian commented on GitHub (Aug 22, 2018): I think your problem could be somehow related to https://github.com/moby/moby/pull/33695

GiteaMirror commented

2025-11-02 04:28:49 -06:00

@ToeiRei commented on GitHub (Aug 23, 2018):

The point which puzzles me here are

tag 1.5 works like a charm
No upgrades on the docker side
No changes to the volumes

So I'm not sure if :nocopy would change things.

My last working build is dated at 2018-07-12 18:13:34 - shortly after that things break. Now the big question I raise is: What changed to the docker image or the entry point which could have broken things that way?

@ToeiRei commented on GitHub (Aug 23, 2018): The point which puzzles me here are - tag 1.5 works like a charm - No upgrades on the docker side - No changes to the volumes So I'm not sure if :nocopy would change things. My last working build is dated at 2018-07-12 18:13:34 - shortly after that things break. Now the big question I raise is: What changed to the docker image or the entry point which could have broken things that way?

GiteaMirror commented

2025-11-02 04:28:49 -06:00

@daviian commented on GitHub (Aug 23, 2018):

The only change that happened since july 12th was b30f6b4099 (diff-05b6053c41a2130afd6fc3b158bda4e6)

@daviian commented on GitHub (Aug 23, 2018): The only change that happened since july 12th was https://github.com/go-gitea/gitea/commit/b30f6b4099d489f88673325b1f9e6e29c823f476#diff-05b6053c41a2130afd6fc3b158bda4e6

GiteaMirror commented

2025-11-02 04:28:50 -06:00

@ToeiRei commented on GitHub (Aug 23, 2018):

That shouldn't be able to break things that hard. It's got to do with chown... at least in some way as I squash root on NFS as usual.

@ToeiRei commented on GitHub (Aug 23, 2018): That shouldn't be able to break things that hard. It's got to do with chown... at least in some way as I squash root on NFS as usual.

GiteaMirror commented

2025-11-02 04:28:51 -06:00

@ToeiRei commented on GitHub (Sep 6, 2018):

anything I am able to help here?

@ToeiRei commented on GitHub (Sep 6, 2018): anything I am able to help here?

GiteaMirror commented

2025-11-02 04:28:51 -06:00

@lafriks commented on GitHub (Sep 10, 2018):

I don't know how gitea docker image would have broken as not much has changed either in build process nor dockerfile. Did you try nocopy? I found this recommendation in multiple places for such problem

@lafriks commented on GitHub (Sep 10, 2018): I don't know how gitea docker image would have broken as not much has changed either in build process nor dockerfile. Did you try nocopy? I found this recommendation in multiple places for such problem

GiteaMirror commented

2025-11-02 04:28:52 -06:00

@ToeiRei commented on GitHub (Sep 10, 2018):

I use nocopy. But the main question still remains: 1.5 and 1.5.1 work perfectly. Why not :latest?

@ToeiRei commented on GitHub (Sep 10, 2018): I use nocopy. But the main question still remains: 1.5 and 1.5.1 work perfectly. Why not :latest?

GiteaMirror commented

2025-11-02 04:28:52 -06:00

@lafriks commented on GitHub (Sep 10, 2018):

I have no explanation for that :(

@lafriks commented on GitHub (Sep 10, 2018): I have no explanation for that :(

GiteaMirror commented

2025-11-02 04:28:53 -06:00

@ToeiRei commented on GitHub (Sep 11, 2018):

Okay. Back to the root(s): I'm going to build it locally.

@ToeiRei commented on GitHub (Sep 11, 2018): Okay. Back to the root(s): I'm going to build it locally.

GiteaMirror commented

2025-11-02 04:28:53 -06:00

@stale[bot] commented on GitHub (Jan 10, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 10, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:28:53 -06:00

@stale[bot] commented on GitHub (Feb 22, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 22, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 12:06:58 -06:00

[PR #2233] [MERGED] Generate small and large logos at 4x resolution #16296

Sign in to join this conversation.