You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Existing docker-compose.yml has the following comment re: container db & groundswell:
version: "3"services:
db:
image: mysql:8.0platform: linux/amd64networks:
- backendexpose:
- 3306environment:
MYSQL_ALLOW_EMPTY_PASSWORD: "yes"MYSQL_USER: towerMYSQL_PASSWORD: towerMYSQL_DATABASE: towerhealthcheck:
test: ["CMD", "mysqladmin" , "ping", "-h", "localhost"]timeout: 20sretries: 10restart: alwaysvolumes:
# To use the pipeline resource optimization service, uncomment the lines below to mount the initialization script# - type: bind# source: ./init.sql# target: /docker-entrypoint-initdb.d/init.sql# Store the MySQL data in a directory on the host
- $HOME/.tower/db/mysql:/var/lib/mysql
Guidance should be added to the groundswell comment that post-deployment activation of groundswell requires manual intervention by the system maintainer.
The text was updated successfully, but these errors were encountered:
Existing docker-compose.yml has the following comment re: container db &
groundswell
:Uncommenting the
init.sql
block won't actually work if the data directory already exists.Guidance should be added to the groundswell comment that post-deployment activation of groundswell requires manual intervention by the system maintainer.
The text was updated successfully, but these errors were encountered: