I am receiving a lot of warnings when creating a new instance of Rancher with a database in a separate docker container. Here are the steps I am using:
# Create initial db volume, db container, and rancher container
docker volume create --name db1
docker run -d --name db1 -e MYSQL_ALLOW_EMPTY_PASSWORD=true -p 3306:3306 -v db1:/var/lib/mysql mysql
docker exec db1 mysql -e "CREATE DATABASE IF NOT EXISTS cattle COLLATE = 'utf8_general_ci' CHARACTER SET = 'utf8';"
docker exec db1 mysql -e "GRANT ALL ON cattle.* TO 'cattle'@'%' IDENTIFIED BY 'cattle';"
docker exec db1 mysql -e "GRANT ALL ON cattle.* TO 'cattle'@'localhost' IDENTIFIED BY 'cattle';"
docker exec db1 bash -c "echo 'bind-address=0.0.0.0' >> /etc/mysql/mysql.conf.d/mysqld.cnf"
docker restart db1
docker run -d --name rancher1 -p 8080:8080 --link db1:db1 rancher/server:latest --db-host db1 --db-port 3306 --db-user cattle --db-pass cattle --db-name cattle
Below are the logs. I see many warnings logs from liquibase during the db migration which takes about five minutes. Does this indicate a problem? Is there some way to avoid this during setup?
CATTLE_AGENT_PACKAGE_HOST_API_URL=/usr/share/cattle/artifacts/host-api.tar.gz
CATTLE_AGENT_PACKAGE_PYTHON_AGENT_URL=/usr/share/cattle/artifacts/go-agent.tar.gz
CATTLE_API_UI_URL=//releases.rancher.com/api-ui/1.0.8
CATTLE_CATTLE_VERSION=v0.181.3
CATTLE_DB_CATTLE_DATABASE=mysql
CATTLE_DB_CATTLE_MYSQL_HOST=db1
CATTLE_DB_CATTLE_MYSQL_NAME=cattle
CATTLE_DB_CATTLE_MYSQL_PORT=3306
CATTLE_DB_CATTLE_USERNAME=cattle
CATTLE_GRAPHITE_HOST=
CATTLE_GRAPHITE_PORT=
CATTLE_HOME=/var/lib/cattle
CATTLE_HOST_API_PROXY_MODE=embedded
CATTLE_LOGBACK_OUTPUT_GELF_HOST=
CATTLE_LOGBACK_OUTPUT_GELF_PORT=
CATTLE_RANCHER_CLI_VERSION=v0.6.1
CATTLE_RANCHER_COMPOSE_VERSION=v0.12.5
CATTLE_RANCHER_SERVER_IMAGE=rancher/server
CATTLE_RANCHER_SERVER_VERSION=v1.6.1
CATTLE_USE_LOCAL_ARTIFACTS=true
DEFAULT_CATTLE_API_UI_CSS_URL=/api-ui/ui.min.css
DEFAULT_CATTLE_API_UI_INDEX=//releases.rancher.com/ui/1.6.5
DEFAULT_CATTLE_API_UI_JS_URL=/api-ui/ui.min.js
DEFAULT_CATTLE_AUTH_SERVICE_EXECUTE=true
DEFAULT_CATTLE_CATALOG_EXECUTE=true
DEFAULT_CATTLE_CATALOG_URL={"catalogs":{"community":{"url":"https://git.rancher.io/community-catalog.git","branch":"master"},"library":{"url":"https://git.rancher.io/rancher-catalog.git","branch":"${RELEASE}"}}}
DEFAULT_CATTLE_COMPOSE_EXECUTOR_EXECUTE=true
DEFAULT_CATTLE_MACHINE_EXECUTE=true
DEFAULT_CATTLE_RANCHER_CLI_DARWIN_URL=https://releases.rancher.com/cli/v0.6.1/rancher-darwin-amd64-v0.6.1.tar.gz
DEFAULT_CATTLE_RANCHER_CLI_LINUX_URL=https://releases.rancher.com/cli/v0.6.1/rancher-linux-amd64-v0.6.1.tar.gz
DEFAULT_CATTLE_RANCHER_CLI_WINDOWS_URL=https://releases.rancher.com/cli/v0.6.1/rancher-windows-386-v0.6.1.zip
DEFAULT_CATTLE_RANCHER_COMPOSE_DARWIN_URL=https://releases.rancher.com/compose/v0.12.5/rancher-compose-darwin-amd64-v0.12.5.tar.gz
DEFAULT_CATTLE_RANCHER_COMPOSE_LINUX_URL=https://releases.rancher.com/compose/v0.12.5/rancher-compose-linux-amd64-v0.12.5.tar.gz
DEFAULT_CATTLE_RANCHER_COMPOSE_WINDOWS_URL=https://releases.rancher.com/compose/v0.12.5/rancher-compose-windows-386-v0.12.5.zip
DEFAULT_CATTLE_SECRETS_API_EXECUTE=true
DEFAULT_CATTLE_WEBHOOK_SERVICE_EXECUTE=true
15:22:41.381 [main] INFO ConsoleStatus - Loading configuration
2017-06-12 15:22:46,169 INFO [main] [ConsoleStatus] Starting DB migration
2017-06-12 15:22:48,723 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,723 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,724 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,724 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,725 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,725 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,726 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,726 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,727 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,728 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,729 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,730 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,731 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,732 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,732 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,733 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,733 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,734 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,734 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,734 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,734 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,734 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
2017-06-12 15:22:48,735 WARN [main] [liquibase] modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use <sql> and re-specify all configuration if this is the case
...