Snap Package Fails to Complete Install After Trying to Register #4070

New Issue

GiteaMirror · 2025-11-02T05:36:32-06:00

GiteaMirror commented

2025-11-02 05:36:32 -06:00

Originally created by @mowestusa on GitHub (Oct 7, 2019).

-->

Gitea version (or commit ref): Snap Package installed
latest/edge | v1.9.0-dev+git29.d578b71 | 27 March 2019
Operating system: Fedora 31 beta Workstation (installed snap package)
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

Description

The snap package appears to install without issue. I can go to localhost:3001 and the Gitea page appears. I click on "Register" to complete the install of Gitea. I accept all the currently checked defaults. I add may administrator user. I click install and the following error screen comes up.
...

Screenshots

Originally created by @mowestusa on GitHub (Oct 7, 2019). --> - Gitea version (or commit ref): Snap Package installed latest/edge | v1.9.0-dev+git29.d578b71 | 27 March 2019 - Operating system: Fedora 31 beta Workstation (installed snap package) - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description The snap package appears to install without issue. I can go to localhost:3001 and the Gitea page appears. I click on "Register" to complete the install of Gitea. I accept all the currently checked defaults. I add may administrator user. I click install and the following error screen comes up. ... ## Screenshots ![191006ErrorScreen-AfterInstallGiteat](https://user-images.githubusercontent.com/31476924/66278663-50745980-e879-11e9-8b49-a923375aeb71.png)

GiteaMirror added the issue/stale label 2025-11-02 05:36:32 -06:00

GiteaMirror closed this issue

2025-11-02 05:36:33 -06:00

GiteaMirror commented

2025-11-02 05:36:33 -06:00

@bagasme commented on GitHub (Oct 8, 2019):

Any log gist?

@bagasme commented on GitHub (Oct 8, 2019): Any log gist?

GiteaMirror commented

2025-11-02 05:36:33 -06:00

@stale[bot] commented on GitHub (Dec 7, 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 (Dec 7, 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 05:36:34 -06:00

@kovariance commented on GitHub (Dec 8, 2019):

I can reproduce this issue. Further attempts to relaunch gitea web fail without error message. The log file show errors like the following:

2019/12/08 14:36:15 [...itea/routers/init.go:95 GlobalInit()] [E] Failed to initialize issue indexer: mkdir indexers: read-only file system

Note that gitea web requires root permissions to run when installed as a snap package.

@kovariance commented on GitHub (Dec 8, 2019): I can reproduce this issue. Further attempts to relaunch `gitea web` fail without error message. The log file show errors like the following: ``` 2019/12/08 14:36:15 [...itea/routers/init.go:95 GlobalInit()] [E] Failed to initialize issue indexer: mkdir indexers: read-only file system ``` Note that `gitea web` requires root permissions to run when installed as a snap package.

GiteaMirror commented

2025-11-02 05:36:34 -06:00

@stale[bot] commented on GitHub (Feb 6, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 6, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:36:34 -06:00

@stale[bot] commented on GitHub (Feb 20, 2020):

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

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

GiteaMirror referenced this issue

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

[PR #4071] [MERGED] Fix drone CLI install link #17225

Sign in to join this conversation.