-
|
Hi, I'm making a gitea compose service with this big docker compose: services:
gitea:
image: gitea/gitea:1.21.10
environment:
- USER_UID=${USER_UID}
- USER_GID=${USER_GID}
- GITEA__database__DB_TYPE=postgres
- GITEA__database__HOST=gitea_db:5432
- GITEA__database__NAME=gitea
- GITEA__database__USER=gitea
- GITEA__database__PASSWD=xxx
restart: always
ports:
- "0.0.0.0:22:22"
- 3000
volumes:
- gitea_data:/data
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
depends_on:
gitea_db:
condition: service_healthy
healthcheck:
test: curl --fail https://git.mydomain.dev/ || exit 1
interval: 40s
timeout: 30s
retries: 3
start_period: 60s
gitea_db:
image: postgres:15
restart: always
environment:
- POSTGRES_USER=gitea
- POSTGRES_PASSWORD=xxx
- POSTGRES_DB=gitea
volumes:
- gitea_db:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U gitea"]
interval: 5s
timeout: 5s
retries: 5
volumes:
gitea_db:
gitea_data:Docker compose isolated deployment is enabled. Seems that this service when deployed doesn't generate a corresponding file in Someone has some idea about the reason why this is happening? PS: I have another problem with another service, again with docker compose, healthcheck configured and https domain. The problems arised when I updated from 0.24.4 to 0.24.9. Have I missed some migrations? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 11 replies
-
|
What do you see when you click Preview compose?
Also as i understand you have to first deploy your service, then change domains and save it and then redeploy. It picks changes up only after redeploy. |
Beta Was this translation helpful? Give feedback.

@eisterman
If a healthcheck fails, traefik removes the service so you will not see it in the dashboard.
To be clear your healthcheck is faulty as you are trying to test a url that hasn't been allocated yet, the healthcheck must be local to the container
I.e before traefik turns on the service the healthcheck has to pass, but it can't pass as traefik hasn't turned it on yet.
Change to localhost:3000 ? Or whatever port the web server is running on