Docker mysql+nacos單機部署的實現(xiàn)步驟
docker 網(wǎng)絡(luò)創(chuàng)建
由于nacos需要訪問mysql的數(shù)據(jù),因此mysql容器和nacos容器之間需要進(jìn)行通信。容器間通信有很多方式,在這里采用同一網(wǎng)絡(luò)下的方式進(jìn)行實現(xiàn)。因此需要創(chuàng)建網(wǎng)絡(luò)。創(chuàng)建網(wǎng)絡(luò)的命令如下:
docker network create --driver bridge nacos-mysql
通過上述命令就創(chuàng)建了一個bridge類型的網(wǎng)絡(luò),該網(wǎng)絡(luò)的名稱為nacos-mysql。創(chuàng)建網(wǎng)絡(luò)完成后可以通過下面命令查看:
docker network ls
mysql容器創(chuàng)建
創(chuàng)建MySQL容器的過程中需要注意兩點:
- 將MySQL容器接入到剛才創(chuàng)建的網(wǎng)絡(luò)中
- 將配置文件容器卷進(jìn)行掛載
MySQL容器的創(chuàng)建如下:
docker run --net=nacos-mysql --restart=always -p 3306:3306 --name=mysql -v D:\docker\MySQL\conf:/etc/mysql/conf.d -v D:\docker\MySQL\log:/var/log/mysql -v D:\docker\MySQL\data:/var/lib/mysql -e MYSQL_ROOT_PASSWORD=password -d mysql:latest
需要注意的是net命令和restart命令都需要緊跟run后,否則容器將啟動失敗。上述代碼執(zhí)行后將啟動了一個mysql容器 ,用戶名為root,密碼為password,接入了nacos-mysql網(wǎng)絡(luò)環(huán)境下,每次docker重啟都將自動運行,映射了端口3306,并且如果D:\docker\MySQL\conf下存在配置文件則應(yīng)該使用該配置文件。但是實際該容器并不會使用掛載出來的配置問題,這是由于mysql容器讀取配置文件時要求該配置文件的權(quán)限并不應(yīng)該為777,777的權(quán)限過高,mysql認(rèn)為該權(quán)限不具備安全性,因此將采用默認(rèn)配置文件進(jìn)行運行系統(tǒng)。這就需要我們進(jìn)入容器內(nèi)容進(jìn)行修改該文件的權(quán)限。進(jìn)入容器的命令如下:
docker exec -it mysql /bin/bash
進(jìn)入指定目錄:
cd /etc/mysql/conf.d
設(shè)置文件權(quán)限(其上級目錄必須時777的權(quán)限):
chmod 664 my.cnf

然后重啟容器,此時,容器重啟時將讀取我們指定的配置文件,如果設(shè)置了啟動服務(wù)是使用到的參數(shù),則需要將mysql上次服務(wù)啟動時創(chuàng)建的data數(shù)據(jù)全部刪除。
nacos部署
mysql部署和mysql類似,主要需要考慮的就是將容器接入nacos-mysql網(wǎng)絡(luò)中,并且將數(shù)據(jù)庫連接設(shè)置為mysql,同一自定義網(wǎng)絡(luò)下的容器可以直接通過容器名進(jìn)行網(wǎng)絡(luò)通信。nacos的啟動命令如下:
docker run -itd --net=nacos-mysql --restart=always -p 8848:8848 -p 9848:9848 -p 9849:9849 --name=nacos -e MODE=standalone -e SPRING_DATASOURCE_PLATFORM=mysql -e MYSQL_SERVICE_HOST=mysql -e MYSQL_SERVICE_PORT=3306 -e MYSQL_SERVICE_DB_NAME=nacos_config -e MYSQL_SERVICE_USER=root -e MYSQL_SERVICE_PASSWORD=password -e MYSQL_DATABASE_NUM=1 nacos/nacos-server
命令中:MYSQL_SERVICE_HOST=mysql即指明了mysql服務(wù)的地址時mysql。上述過程完成了mysql和nacos的docker部署,在部署完成之后,我們可以查看網(wǎng)絡(luò)狀態(tài),驗證兩個容器是否接入到了指定自定義網(wǎng)絡(luò)中,命令:
docker inspect network nacos-mysql

至此,我們發(fā)現(xiàn)兩個容器都在同一個網(wǎng)絡(luò)中了。nacos的mysql數(shù)據(jù)庫表結(jié)構(gòu)如下所示:
/*
Navicat Premium Data Transfer
Source Server : localhost
Source Server Type : MySQL
Source Server Version : 80031
Source Host : localhost:3306
Source Schema : nacos_config
Target Server Type : MySQL
Target Server Version : 80031
File Encoding : 65001
Date: 08/08/2023 23:10:27
*/
SET NAMES utf8mb4;
SET FOREIGN_KEY_CHECKS = 0;
-- ----------------------------
-- Table structure for config_info
-- ----------------------------
DROP TABLE IF EXISTS `config_info`;
CREATE TABLE `config_info` (
`id` bigint NOT NULL AUTO_INCREMENT COMMENT 'id',
`data_id` varchar(255) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'data_id',
`group_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL,
`content` longtext CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'content',
`md5` varchar(32) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL COMMENT 'md5',
`gmt_create` datetime NOT NULL DEFAULT '2010-05-05 00:00:00' COMMENT '鍒涘緩鏃墮棿',
`gmt_modified` datetime NOT NULL DEFAULT '2010-05-05 00:00:00' COMMENT '淇?敼鏃墮棿',
`src_user` text CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL COMMENT 'source user',
`src_ip` varchar(20) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL COMMENT 'source ip',
`app_name` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL,
`tenant_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT '' COMMENT '縐熸埛瀛楁?',
`c_desc` varchar(256) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL,
`c_use` varchar(64) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL,
`effect` varchar(64) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL,
`type` varchar(64) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL,
`c_schema` text CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL,
`encrypted_data_key` text CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT '縐橀挜',
PRIMARY KEY (`id`) USING BTREE,
UNIQUE INDEX `uk_configinfo_datagrouptenant`(`data_id` ASC, `group_id` ASC, `tenant_id` ASC) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 206 CHARACTER SET = utf8mb3 COLLATE = utf8mb3_bin COMMENT = 'config_info' ROW_FORMAT = DYNAMIC;
-- ----------------------------
-- Table structure for config_info_aggr
-- ----------------------------
DROP TABLE IF EXISTS `config_info_aggr`;
CREATE TABLE `config_info_aggr` (
`id` bigint NOT NULL AUTO_INCREMENT COMMENT 'id',
`data_id` varchar(255) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'data_id',
`group_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'group_id',
`datum_id` varchar(255) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'datum_id',
`content` longtext CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT '鍐呭?',
`gmt_modified` datetime NOT NULL COMMENT '淇?敼鏃墮棿',
`app_name` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL,
`tenant_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT '' COMMENT '縐熸埛瀛楁?',
PRIMARY KEY (`id`) USING BTREE,
UNIQUE INDEX `uk_configinfoaggr_datagrouptenantdatum`(`data_id` ASC, `group_id` ASC, `tenant_id` ASC, `datum_id` ASC) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 1 CHARACTER SET = utf8mb3 COLLATE = utf8mb3_bin COMMENT = '澧炲姞縐熸埛瀛楁?' ROW_FORMAT = DYNAMIC;
-- ----------------------------
-- Records of config_info_aggr
-- ----------------------------
-- ----------------------------
-- Table structure for config_info_beta
-- ----------------------------
DROP TABLE IF EXISTS `config_info_beta`;
CREATE TABLE `config_info_beta` (
`id` bigint NOT NULL AUTO_INCREMENT COMMENT 'id',
`data_id` varchar(255) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'data_id',
`group_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'group_id',
`app_name` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL COMMENT 'app_name',
`content` longtext CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'content',
`beta_ips` varchar(1024) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL COMMENT 'betaIps',
`md5` varchar(32) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL COMMENT 'md5',
`gmt_create` datetime NOT NULL DEFAULT '2010-05-05 00:00:00' COMMENT '鍒涘緩鏃墮棿',
`gmt_modified` datetime NOT NULL DEFAULT '2010-05-05 00:00:00' COMMENT '淇?敼鏃墮棿',
`src_user` text CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL COMMENT 'source user',
`src_ip` varchar(20) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL COMMENT 'source ip',
`tenant_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT '' COMMENT '縐熸埛瀛楁?',
`encrypted_data_key` text CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT '縐橀挜',
PRIMARY KEY (`id`) USING BTREE,
UNIQUE INDEX `uk_configinfobeta_datagrouptenant`(`data_id` ASC, `group_id` ASC, `tenant_id` ASC) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 1 CHARACTER SET = utf8mb3 COLLATE = utf8mb3_bin COMMENT = 'config_info_beta' ROW_FORMAT = DYNAMIC;
-- ----------------------------
-- Records of config_info_beta
-- ----------------------------
-- ----------------------------
-- Table structure for config_info_tag
-- ----------------------------
DROP TABLE IF EXISTS `config_info_tag`;
CREATE TABLE `config_info_tag` (
`id` bigint NOT NULL AUTO_INCREMENT COMMENT 'id',
`data_id` varchar(255) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'data_id',
`group_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'group_id',
`tenant_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT '' COMMENT 'tenant_id',
`tag_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'tag_id',
`app_name` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL COMMENT 'app_name',
`content` longtext CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'content',
`md5` varchar(32) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL COMMENT 'md5',
`gmt_create` datetime NOT NULL DEFAULT '2010-05-05 00:00:00' COMMENT '鍒涘緩鏃墮棿',
`gmt_modified` datetime NOT NULL DEFAULT '2010-05-05 00:00:00' COMMENT '淇?敼鏃墮棿',
`src_user` text CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL COMMENT 'source user',
`src_ip` varchar(20) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL COMMENT 'source ip',
PRIMARY KEY (`id`) USING BTREE,
UNIQUE INDEX `uk_configinfotag_datagrouptenanttag`(`data_id` ASC, `group_id` ASC, `tenant_id` ASC, `tag_id` ASC) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 1 CHARACTER SET = utf8mb3 COLLATE = utf8mb3_bin COMMENT = 'config_info_tag' ROW_FORMAT = DYNAMIC;
-- ----------------------------
-- Records of config_info_tag
-- ----------------------------
-- ----------------------------
-- Table structure for config_tags_relation
-- ----------------------------
DROP TABLE IF EXISTS `config_tags_relation`;
CREATE TABLE `config_tags_relation` (
`id` bigint NOT NULL COMMENT 'id',
`tag_name` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'tag_name',
`tag_type` varchar(64) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL COMMENT 'tag_type',
`data_id` varchar(255) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'data_id',
`group_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'group_id',
`tenant_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT '' COMMENT 'tenant_id',
`nid` bigint NOT NULL AUTO_INCREMENT,
PRIMARY KEY (`nid`) USING BTREE,
UNIQUE INDEX `uk_configtagrelation_configidtag`(`id` ASC, `tag_name` ASC, `tag_type` ASC) USING BTREE,
INDEX `idx_tenant_id`(`tenant_id` ASC) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 1 CHARACTER SET = utf8mb3 COLLATE = utf8mb3_bin COMMENT = 'config_tag_relation' ROW_FORMAT = DYNAMIC;
-- ----------------------------
-- Records of config_tags_relation
-- ----------------------------
-- ----------------------------
-- Table structure for group_capacity
-- ----------------------------
DROP TABLE IF EXISTS `group_capacity`;
CREATE TABLE `group_capacity` (
`id` bigint UNSIGNED NOT NULL AUTO_INCREMENT COMMENT '涓婚敭ID',
`group_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL DEFAULT '' COMMENT 'Group ID錛岀┖瀛楃?琛ㄧず鏁翠釜闆嗙兢',
`quota` int UNSIGNED NOT NULL DEFAULT 0 COMMENT '閰嶉?錛?琛ㄧず浣跨敤榛樿?鍊',
`usage` int UNSIGNED NOT NULL DEFAULT 0 COMMENT '浣跨敤閲',
`max_size` int UNSIGNED NOT NULL DEFAULT 0 COMMENT '鍗曚釜閰嶇疆澶у皬涓婇檺錛屽崟浣嶄負(fù)瀛楄妭錛?琛ㄧず浣跨敤榛樿?鍊',
`max_aggr_count` int UNSIGNED NOT NULL DEFAULT 0 COMMENT '鑱氬悎瀛愰厤緗?渶澶т釜鏁幫紝錛?琛ㄧず浣跨敤榛樿?鍊',
`max_aggr_size` int UNSIGNED NOT NULL DEFAULT 0 COMMENT '鍗曚釜鑱氬悎鏁版嵁鐨勫瓙閰嶇疆澶у皬涓婇檺錛屽崟浣嶄負(fù)瀛楄妭錛?琛ㄧず浣跨敤榛樿?鍊',
`max_history_count` int UNSIGNED NOT NULL DEFAULT 0 COMMENT '鏈?ぇ鍙樻洿鍘嗗彶鏁伴噺',
`gmt_create` datetime NOT NULL DEFAULT '2010-05-05 00:00:00' COMMENT '鍒涘緩鏃墮棿',
`gmt_modified` datetime NOT NULL DEFAULT '2010-05-05 00:00:00' COMMENT '淇?敼鏃墮棿',
PRIMARY KEY (`id`) USING BTREE,
UNIQUE INDEX `uk_group_id`(`group_id` ASC) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 1 CHARACTER SET = utf8mb3 COLLATE = utf8mb3_bin COMMENT = '闆嗙兢銆佸悇Group瀹歸噺淇℃伅琛' ROW_FORMAT = DYNAMIC;
-- ----------------------------
-- Records of group_capacity
-- ----------------------------
-- ----------------------------
-- Table structure for his_config_info
-- ----------------------------
DROP TABLE IF EXISTS `his_config_info`;
CREATE TABLE `his_config_info` (
`id` bigint UNSIGNED NOT NULL,
`nid` bigint UNSIGNED NOT NULL AUTO_INCREMENT,
`data_id` varchar(255) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL,
`group_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL,
`app_name` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL COMMENT 'app_name',
`content` longtext CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL,
`md5` varchar(32) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL,
`gmt_create` datetime NOT NULL DEFAULT '2010-05-05 00:00:00',
`gmt_modified` datetime NOT NULL DEFAULT '2010-05-05 00:00:00',
`src_user` text CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL,
`src_ip` varchar(20) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL,
`op_type` char(10) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL,
`tenant_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT '' COMMENT '縐熸埛瀛楁?',
`encrypted_data_key` text CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT '縐橀挜',
PRIMARY KEY (`nid`) USING BTREE,
INDEX `idx_gmt_create`(`gmt_create` ASC) USING BTREE,
INDEX `idx_gmt_modified`(`gmt_modified` ASC) USING BTREE,
INDEX `idx_did`(`data_id` ASC) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 231 CHARACTER SET = utf8mb3 COLLATE = utf8mb3_bin COMMENT = '澶氱?鎴鋒敼閫' ROW_FORMAT = DYNAMIC;
-- ----------------------------
-- Table structure for permissions
-- ----------------------------
DROP TABLE IF EXISTS `permissions`;
CREATE TABLE `permissions` (
`role` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,
`resource` varchar(512) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,
`action` varchar(8) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,
UNIQUE INDEX `uk_role_permission`(`role` ASC, `resource` ASC, `action` ASC) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC;
-- ----------------------------
-- Records of permissions
-- ----------------------------
-- ----------------------------
-- Table structure for roles
-- ----------------------------
DROP TABLE IF EXISTS `roles`;
CREATE TABLE `roles` (
`username` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,
`role` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,
UNIQUE INDEX `uk_username_role`(`username` ASC, `role` ASC) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC;
-- ----------------------------
-- Records of roles
-- ----------------------------
INSERT INTO `roles` VALUES ('nacos', 'ROLE_ADMIN');
-- ----------------------------
-- Table structure for tenant_capacity
-- ----------------------------
DROP TABLE IF EXISTS `tenant_capacity`;
CREATE TABLE `tenant_capacity` (
`id` bigint UNSIGNED NOT NULL AUTO_INCREMENT COMMENT '涓婚敭ID',
`tenant_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL DEFAULT '' COMMENT 'Tenant ID',
`quota` int UNSIGNED NOT NULL DEFAULT 0 COMMENT '閰嶉?錛?琛ㄧず浣跨敤榛樿?鍊',
`usage` int UNSIGNED NOT NULL DEFAULT 0 COMMENT '浣跨敤閲',
`max_size` int UNSIGNED NOT NULL DEFAULT 0 COMMENT '鍗曚釜閰嶇疆澶у皬涓婇檺錛屽崟浣嶄負(fù)瀛楄妭錛?琛ㄧず浣跨敤榛樿?鍊',
`max_aggr_count` int UNSIGNED NOT NULL DEFAULT 0 COMMENT '鑱氬悎瀛愰厤緗?渶澶т釜鏁',
`max_aggr_size` int UNSIGNED NOT NULL DEFAULT 0 COMMENT '鍗曚釜鑱氬悎鏁版嵁鐨勫瓙閰嶇疆澶у皬涓婇檺錛屽崟浣嶄負(fù)瀛楄妭錛?琛ㄧず浣跨敤榛樿?鍊',
`max_history_count` int UNSIGNED NOT NULL DEFAULT 0 COMMENT '鏈?ぇ鍙樻洿鍘嗗彶鏁伴噺',
`gmt_create` datetime NOT NULL DEFAULT '2010-05-05 00:00:00' COMMENT '鍒涘緩鏃墮棿',
`gmt_modified` datetime NOT NULL DEFAULT '2010-05-05 00:00:00' COMMENT '淇?敼鏃墮棿',
PRIMARY KEY (`id`) USING BTREE,
UNIQUE INDEX `uk_tenant_id`(`tenant_id` ASC) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 1 CHARACTER SET = utf8mb3 COLLATE = utf8mb3_bin COMMENT = '縐熸埛瀹歸噺淇℃伅琛' ROW_FORMAT = DYNAMIC;
-- ----------------------------
-- Records of tenant_capacity
-- ----------------------------
-- ----------------------------
-- Table structure for tenant_info
-- ----------------------------
DROP TABLE IF EXISTS `tenant_info`;
CREATE TABLE `tenant_info` (
`id` bigint NOT NULL AUTO_INCREMENT COMMENT 'id',
`kp` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NOT NULL COMMENT 'kp',
`tenant_id` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT '' COMMENT 'tenant_id',
`tenant_name` varchar(128) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT '' COMMENT 'tenant_name',
`tenant_desc` varchar(256) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL COMMENT 'tenant_desc',
`create_source` varchar(32) CHARACTER SET utf8mb3 COLLATE utf8mb3_bin NULL DEFAULT NULL COMMENT 'create_source',
`gmt_create` bigint NOT NULL COMMENT '鍒涘緩鏃墮棿',
`gmt_modified` bigint NOT NULL COMMENT '淇?敼鏃墮棿',
PRIMARY KEY (`id`) USING BTREE,
UNIQUE INDEX `uk_tenant_info_kptenantid`(`kp` ASC, `tenant_id` ASC) USING BTREE,
INDEX `idx_tenant_id`(`tenant_id` ASC) USING BTREE
) ENGINE = InnoDB AUTO_INCREMENT = 2 CHARACTER SET = utf8mb3 COLLATE = utf8mb3_bin COMMENT = 'tenant_info' ROW_FORMAT = DYNAMIC;
-- ----------------------------
-- Table structure for users
-- ----------------------------
DROP TABLE IF EXISTS `users`;
CREATE TABLE `users` (
`username` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,
`password` varchar(500) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci NOT NULL,
`enabled` tinyint(1) NOT NULL,
PRIMARY KEY (`username`) USING BTREE
) ENGINE = InnoDB CHARACTER SET = utf8mb4 COLLATE = utf8mb4_0900_ai_ci ROW_FORMAT = DYNAMIC;
-- ----------------------------
-- Records of users
-- ----------------------------
INSERT INTO `users` VALUES ('nacos', '$2a$10$EuWPZHzz32dJN7jexM34MOeYirDdFAZm2kuWj7VEOJhhZkDrxfvUu', 1);
SET FOREIGN_KEY_CHECKS = 1;請忽略中文亂碼問題(_),用戶名和密碼都為nacos。
到此這篇關(guān)于Docker mysql+nacos單機部署的實現(xiàn)步驟的文章就介紹到這了,更多相關(guān)Docker mysql+nacos單機部署內(nèi)容請搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家!
相關(guān)文章
Docker自動化構(gòu)建Automated Build實現(xiàn)過程圖解
這篇文章主要介紹了Docker自動化構(gòu)建Automated Build實現(xiàn)過程圖解,文中通過示例代碼介紹的非常詳細(xì),對大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價值,需要的朋友可以參考下2020-10-10
docker prune命令可定時清理不常用數(shù)據(jù)的實現(xiàn)
磁盤使用過久就會導(dǎo)致磁盤空間越來越小,這時候就需要刪除不相關(guān)的數(shù)據(jù)來釋放磁盤空間,本文主要使用docker prune命令可定時清理不常用數(shù)據(jù)的實現(xiàn),感興趣的可以了解一下2021-10-10
Docker安裝Minio+SpringBoot上傳下載文件方式
本文主要介紹了如何通過Docker安裝Minio并進(jìn)行訪問測試,同時也講解了如何在SpringBoot中上傳文件到Minio,內(nèi)容包含了pom文件引入依賴,application.properties配置,Minio配置,MinioClinet,FileService,FileServiceImpl的配置2024-10-10
Docker訪問容器中的Spring Boot日志的幾種方法
在本文中,我們將演示如何在Docker容器中訪問Spring Boot日志,文中通過示例代碼介紹的非常詳細(xì),對大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價值,需要的朋友們下面隨著小編來一起學(xué)習(xí)學(xué)習(xí)吧2026-04-04
docker安裝Jenkins執(zhí)行構(gòu)建jar運行方式
這篇文章主要介紹了docker安裝Jenkins執(zhí)行構(gòu)建jar運行方式,具有很好的參考價值,希望對大家有所幫助,如有錯誤或未考慮完全的地方,望不吝賜教2024-05-05
Docker swarm集群部署過程詳解(包含compose.yml文件詳情)
Docker Swarm是Docker的集群管理工具,支持服務(wù)部署、副本調(diào)度、Stack管理(基于Compose文件),包含初始化集群、節(jié)點添加、服務(wù)更新、資源清理等操作,確保容器化應(yīng)用的高效運行,本文給大家介紹Docker swarm集群部署包含compose.yml文件詳情,感興趣的朋友一起看看吧2025-07-07
Docker中關(guān)于Namespace隔離機制全面解析
為了更好地理解容器的運行原理,本篇文章將會以?Linux?宿主機為例,介紹容器的底層技術(shù),包括容器的命名空間、控制組、聯(lián)合文件系統(tǒng)等,需要的朋友可以參考下2022-06-06
使用docker compose搭建consul集群環(huán)境的例子
consul是HashCorp公司推出使用go語言編寫的開源工具,用于實現(xiàn)分布式系統(tǒng)的服務(wù)發(fā)現(xiàn)與配置,今天給大家普及使用docker compose搭建consul集群環(huán)境的方法及consul基本知識講解,感興趣的朋友一起看看吧2021-06-06

