Gitea 1.1.0 docker image throws panic errors on startup #578

New Issue

GiteaMirror · 2025-11-02T03:28:41-06:00

GiteaMirror commented

2025-11-02 03:28:41 -06:00

Originally created by @TheRaz on GitHub (Mar 27, 2017).

Gitea version (or commit ref): 1.1.0
Git version: 2.8.3
Operating system: Debian 8
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: https://gist.github.com/TheRaz/f0527ea6f69f84c38db34c056fb3e483

Description

When the gitea docker 1.1.0 image is started it starts throwing go panic errors, the errors does not occur on 1.1 or 1.0 image, log goes into infinite loop and gitea wont start.

The image has been working for around 10 days after update before the errors started.

Originally created by @TheRaz on GitHub (Mar 27, 2017). - Gitea version (or commit ref): 1.1.0 - Git version: 2.8.3 - Operating system: Debian 8 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: https://gist.github.com/TheRaz/f0527ea6f69f84c38db34c056fb3e483 ## Description When the gitea docker 1.1.0 image is started it starts throwing go panic errors, the errors does not occur on 1.1 or 1.0 image, log goes into infinite loop and gitea wont start. The image has been working for around 10 days after update before the errors started.

GiteaMirror added the type/bug label 2025-11-02 03:28:41 -06:00

GiteaMirror closed this issue

2025-11-02 03:28:42 -06:00

GiteaMirror commented

2025-11-02 03:28:42 -06:00

@sapk commented on GitHub (Apr 30, 2017):

Hi, since there were some update on the docker image done.
Is this bug still existing ?

@sapk commented on GitHub (Apr 30, 2017): Hi, since there were some update on the docker image done. Is this bug still existing ?

GiteaMirror commented

2025-11-02 03:28:42 -06:00

@ptman commented on GitHub (May 4, 2017):

I don't have a problem with the docker image, so something is still missing before anyone can reproduce it.

@ptman commented on GitHub (May 4, 2017): I don't have a problem with the docker image, so something is still missing before anyone can reproduce it.

GiteaMirror commented

2025-11-02 03:28:43 -06:00

@TheRaz commented on GitHub (May 4, 2017):

Sorry for the late answer, I'm no longer with the same employer so i can't reproduce this error again. The panic occurred as soon as the docker image loaded but that's all the info i still have access to.
My guess is that it was caused by some problem with the saved data as it only occurred after 10 days of running the image.

@TheRaz commented on GitHub (May 4, 2017): Sorry for the late answer, I'm no longer with the same employer so i can't reproduce this error again. The panic occurred as soon as the docker image loaded but that's all the info i still have access to. My guess is that it was caused by some problem with the saved data as it only occurred after 10 days of running the image.

GiteaMirror commented

2025-11-02 03:28:43 -06:00

@DblK commented on GitHub (May 22, 2017):

Can we close this issue?

@DblK commented on GitHub (May 22, 2017): Can we close this issue?

GiteaMirror referenced this issue

2025-11-02 11:47:07 -06:00

[PR #578] [MERGED] Fix config session missing data row & resolved #517 #15464

Sign in to join this conversation.