raspher
commented
1 year ago Have reproduced, but dived deeper.
I've created my gitea.yml setup, made a lot of changes and... Just discovered that if you have existing docker volume, changes made to .yml file won't take effect.
- Make
ymlfile and specify SSH options, you must use docker volume to store your data - Build and start container
- Change options in
.ymlfile - Destroy all docker data but don't touch existing volume
- rebuild and start container
- You'll see that making changes in
.ymlfile doesn't take any effect
Cheers and please fix it, as it's impossible to :
- change configuration in .yml file, you'll need to somehow get into container that have mounted used volume and change
.inifile by hand - it's hard to recover persisted data with different configuration while making changes to
ymlfile - even changing domain in
ymlwoudn't have any effect
_Even changing APPNAME does not work. By removing volume which result in data loss changes in yml file will have effect.
It's not only docker-compose issue, but docker in general
Funny fact: declaring SSH_LISTEN_PORT=2222 works, but GITEA_server_SSH_LISTEN_PORT=2222 does not, even if i've removed volume.
My gitea.yml (docker-compose)
version: "3"
networks:
gitea:
external: false
services:
server:
env_file:
- gitea.env
image: gitea/gitea:1.17.3
container_name: gitea
environment:
- RUN_MODE=prod
- APP_NAME=test
# Repository
- GITEA__repository__FORCE_PRIVATE=true
- GITEA__repository__DEFAULT_PUSH_CREATE_PRIVATE=true
- GITEA__repository__DISABLE_HTTP_GIT=true
- GITEA__repository__DEFAULT_BRANCH=master
- GITEA__repository.pull-request__DEFAULT_MERGE_STYLE="squash"
- GITEA__repository.pull-request__DEFAULT_MERGE_MESSAGE_COMMITS_LIMIT=-1
- GITEA__repository.pull-request__DEFAULT_MERGE_MESSAGE_ALL_AUTHORS=true
- GITEA__repository.pull-request__ADD_CO_COMMITTER_TRAILERS=true
- GITEA__repository.release__ALLOWED_TYPES="*/*"
# UI
- GITEA__ui__EXPLORE_PAGING_NUM=50
- GITEA__ui__ISSUE_PAGING_NUM=50
- GITEA__ui__MEMBERS_PAGING_NUM=50
- GITEA__ui__FEED_MAX_COMMIT_NUM=10
- GITEA__ui__FEED_PAGING_NUM=50
- GITEA__ui__SITEMAP_PAGING_NUM=50
- GITEA__ui__DEFAULT_SHOW_FULL_NAME=50
- GITEA__ui__DEFAULT_SHOW_FULL_NAME=true
- GITEA__service__DEFAULT_ORG_MEMBER_VISIBLE=true
- GITEA__ui.meta__AUTHOR="UrnTea"
- GITEA__ui.meta__DESCRIPTION="selfhosted Gitea"
- GITEA__ui.meta__KEYWORDS="git,gitea,self-hosted"
# Server
- GITEA__server__HTTP_ADDR="0.0.0.0"
- GITEA__server__HTTP_PORT="3000"
- GITEA__server__START_SSH_SERVER=false
- GITEA__server__SSH_PORT=22
- GITEA__server__SSH_LISTEN_HOST="0.0.0.0"
- GITEA__server__SSH_LISTEN_PORT=2222
- GITEA__database__DB_TYPE="sqlite3"
# Security
- GITEA__security__SECRET_KEY=${GITEA__security__SECRET_KEY}
- GITEA__security__INTERNAL_TOKEN=${GITEA__security__INTERNAL_TOKEN}
- GITEA__security__PASSWORD_HASH_ALGO="bcrypt"
- GITEA__security__MIN_PASSWORD_LENGTH=8
- GITEA__security__PASSWORD_COMPLEXITY="lower,upper,digit,spec"
- GITEA__security__PASSWORD_CHECK_PWN=true
- GITEA__service__DISABLE_REGISTRATION=true
- GITEA__service.explore__REQUIRE_SIGNIN_VIEW=true
# Proxy
- GITEA__security__REVERSE_PROXY_LIMIT=1
- GITEA__security__REVERSE_PROXY_TRUSTED_PROXIES="127.0.0.0/8,::1/128"
# Webhooks
- GITEA__webhook__DELIVER_TIMEOUT=10 #secs
- GITEA__webhook__PAGING_NUM=20
# Cache
- GITEA__cache__ITEM_TTL=1h
restart: always
networks:
- gitea
volumes:
- gitea-data:/data
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
ports:
- "3000:3000"
- "22:2222"
volumes:
gitea-data:
voidzero
[x]):Description
I have a host with multiple interfaces and addresses. Therefore I'd like to have the dedicated SSH daemon listen on only two particular addresses. In my case a IPv4 and a IPv6 address.
The configuration parameter
SSH_LISTEN_HOSTdoes not seem to accept more than one address and defining it on a second line will overwrite the first one.I tried the following combinations:
Try 1:
Result try 1:
Try 2:
Result:
Try 3:
Result:
Try 4:
Result: Will only listen to 10.10.10.10 but not 2001:0db8:85a3:08d3:1319:8a2e:0370
Workaround: comment
SSH_LISTEN_HOSTso the gitea SSH daemon will listen on every device and firewall undesired access.