Infos:
- Used Zammad version: 6.4.1
- Used Zammad installation type: docker compose
- Operating system: Debian
- Browser + version: Firefox, 133
Expected behavior:
- Everything starts as it should
Actual behavior:
When starting the stack, the init
container seems to exit successfully (exit code 0). The last few log messages:
init-1 | Reloading data...
init-1 | - Chat::Session...
done in 0 seconds.
init-1 | - Cti::Log...
done in 0 seconds.
init-1 | - Group...
done in 0 seconds.
init-1 | - KnowledgeBase::Answer::Translation...
done in 0 seconds.
init-1 | - KnowledgeBase::Category::Translation...
done in 0 seconds.
init-1 | - KnowledgeBase::Translation...
done in 0 seconds.
init-1 | - Organization...
done in 0 seconds.
init-1 | - StatsStore...
done in 0 seconds.
init-1 | - Ticket::Priority...
done in 0 seconds.
init-1 | - Ticket::State...
done in 0 seconds.
init-1 | - Ticket...
done in 0 seconds.
init-1 | - User...
done in 0 seconds.
However, the nginx container does not start. It only logs this every few seconds:
waiting for init container to finish install or update...
How can the init container finish install or update when it has already exited?
Steps to reproduce the behavior:
- Clone the docker compose repo
- Run it