文章目录
1、docker pull nginx
:下载nginx
2、docker run --name mynginx -d nginx
: 运行nginx实例
3、新建nginx目录在本地
cd /usr/local/
mkdir nginx
3、复制nginx的目录到本地,命令如下
//复制配置文件到本地
docker cp mynginx:/etc/nginx /usr/share/nginx/conf/
//复制html目录到本地
docker cp mynginx:/usr/share/nginx/html /usr/share/nginx/html
//复制日志到到本地
docker cp mynginx:/var/log/nginx /usr/share/nginx/logs
4、挂载目录并且启动nginx,如下:
docker run --name mynginx -p 80:80 -v /usr/share/nginx/html:/usr/share/nginx/html -v /usr/share/nginx/conf:/etc/nginx -v /usr/share/nginx/logs:/var/log/nginx/ -d nginx
5、安装完成,此时的docker容器中的nginx的html路径就和本地的/usr/share/nginx/html
对应了,如果需要建立目录,只需要在本地目录下建立就会自动更新到容器中
docker pull tomcat:8-jre8
: 现在镜像(tomcat8,jdk的版本8)docker run --name tom -d -p 8081:8080 41a54fe1f79d
docker cp tom:/usr/local/tomcat/conf /usr/local/tomcat/conf
docker cp tom:/usr/local/tomcat/lib /usr/local/tomcat/lib
docker cp tom:/usr/local/tomcat/webapps /usr/local/tomcat/webapps
docker cp tom:/usr/local/tomcat/bin /usr/local/tomcat/bin
docker cp tom:/usr/local/tomcat/work /usr/local/tomcat/work
docker cp tom:/usr/local/tomcat/temp /usr/local/tomcat/temp
docker cp tom:/usr/local/tomcat/logs /usr/local/tomcat/logs
docker run --name tom -p 8081:8080 -v /usr/local/tomcat/conf:/usr/local/tomcat/conf -v /usr/local/tomcat/lib:/usr/local/tomcat/lib -v /usr/local/tomcat/webapps:/usr/local/tomcat/webapps -v /usr/local/tomcat/bin:/usr/local/tomcat/bin -v /usr/local/tomcat/work:/usr/local/tomcat/work -v /usr/local/tomcat/temp:/usr/local/tomcat/temp -v /usr/local/tomcat/logs:/usr/local/tomcat/logs -d 41a54fe1f79d
docker pull mysql:5.7.24
docker run --name mysql -p 3306:3306 -e MYSQL_ROOT_PASSWORD=12345 -d 702fb0b7837f
docker cp mysql:/sbin /usr/local/mysql/bin
docker cp mysql:/var/lib/mysql /usr/local/mysql/data
docker cp mysql:/etc/mysql /usr/local/mysql/conf
docker run --name mysql -p 3306:3306 -v /usr/local/mysql/bin:/sbin -v /usr/local/mysql/data:/var/lib/mysql -v /usr/local/mysql/conf:/etc/mysql -e MYSQL_ROOT_PASSWORD=12345 -d 702fb0b7837f
[mysql]
default-character-set=utf8
# SERVER SECTION
# ----------------------------------------------------------------------
#
# The following options will be read by the MySQL Server. Make sure that
# you have installed the server correctly (see above) so it reads this
# file.
#
[mysqld]
# The TCP/IP Port the MySQL Server will listen on
port=3306
#Path to installation directory. All paths are usually resolved relative to this.
#basedir="E:/Java/Mysql/"
#Path to the database root
datadir="/usr/local/mysql/data"
# The default character set that will be used when a new schema or table is
# created and no character set is defined
character-set-server=utf8
# The default storage engine that will be used when create new tables when
default-storage-engine=INNODB
# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=1000
# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=0
# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
#table_cache=256
# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=35M
# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=8
#*** MyISAM Specific options
# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G
# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=69M
# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=55M
# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=64K
read_rnd_buffer_size=256K
# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=256K
#*** INNODB Specific options ***
# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
#skip-innodb
# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
#innodb_additional_mem_pool_size=3M
# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
#innodb_flush_log_at_trx_commit=1
# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
#innodb_log_buffer_size=2M
# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
#innodb_buffer_pool_size=107M
# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
#innodb_log_file_size=54M
# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
#innodb_thread_concurrency=18