docker基础篇-docker的安装、配置、卸载，自定义镜像和搭建公有和私有镜像仓库
本篇主要是docker的安装、配置、卸载，自定义镜像和搭建公有和私有镜像仓库，以及常规软件安装示例。
mysql主从，redis主从搭建，Dockerfile解析及docker-compose编排等见另一篇文章：
docker高级篇(mysql主从，redis主从搭建，Dockerfile解析及docker-compose编排)
docker基础篇
-
- 一、docker的安装卸载
-
-
- 1、linux内核要求
- 2、安装步骤
-
- 2-1. 卸载旧版本
- 2-2.yum安装gcc相关
- 2-3.安装需要的软件包
- 2-4.设置stable镜像仓库
- 2-5.更新yum软件包索引
- 2-6.安装docker ce
- 2-7.启动docker
- 2-8.测试
- 3、卸载
-
- 二、配置阿里镜像
- 三、docker常用命令
-
-
- 1.帮助启动类命令
- 2.镜像命令
- 3.容器命令
-
- 四、自定义docker镜像
-
-
- 1. 创建本地镜像
- 2. 将镜像上传到阿里云镜像仓库
-
- 2-1. 创建命名空间
- 2-2. 创建镜像仓库
- 2-3. 得到推送和拉取的相关指令
- 2-4. 执行推送命令
- 2-5. 阿里云镜像仓库查看
- 2-6. 测试拉取
- 3. 将镜像上传到本地私有仓库（docker registry）
-
- 3-1.下载镜像docker registry：`docker pull registry`
- 3-2. 运行私有库registry，相当于本地有个私有的docker hub：`docker run -d -p 5000:5000 -v /zzyyuse/myregistry/:/tmp/registry/ --privileged=true registry`
- 3-3. 创建一个新的镜像，上传到本地私有仓库
- 3-4. curl验证私有库上有哪些镜像：`curl -XGET http://192.168.64.128:5000/v2/_catalog`
- 3-5. 修改新镜像达到私服规范：`docker tag 本地镜像名:相应的TAG ip:port/repostry:TAG`
- 3-6. 修改配置文件支持http：`"insecure-registries":["192.168.64.128:5000"]`，注意不要忘记逗号。若`修改后不生效，重启docker`
- 3-7. push到私服：`docker push 192.168.64.128:5000/gonglubuntu:1.9`
- 3-8. curl验证私有库上有哪些镜像：`curl -XGET http://192.168.64.128:5000/v2/_catalog`
- 3-9. pull到本地运行
-
- 五、docker 容器数据卷
- 六、docker常规安装简介
-
-
- 1. 安装Tomcat
- 2.安装mysql
- 3. 安装Redis
-
一、docker的安装卸载
1、linux内核要求
cat /etc/redhat-release
2、安装步骤
官网地址：https://docs.docker.com/engine/install/centos/
2-1. 卸载旧版本
yum remove docker \
docker-client \
docker-client-latest \
docker-common \
docker-latest \
docker-latest-logrotate \
docker-logrotate \
docker-engine
2-2.yum安装gcc相关
yum -y install gcc
yum -y install gcc-c++
2-3.安装需要的软件包
yum install -y yum-utils
2-4.设置stable镜像仓库
yum-config-manager --add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
2-5.更新yum软件包索引
yum makecache fast
2-6.安装docker ce
yum install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
2-7.启动docker
systemctl start docker
2-8.测试
docker version
docker run hello-world
3、卸载
systemctl stop docker
yum remove docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin docker-ce-rootless-extras
rm -rf /var/lib/docker
rm -rf /var/lib/containerd
二、配置阿里镜像
1.登录自己的阿里云–>容器镜像服务–>镜像加速器；查看自己的镜像加速地址
2.执行界面的脚本指令
mkdir -p /etc/docker
vim /etc/docker/daemon.json
将下面json加入daemon.json
{
"registry-mirrors": ["https://fhtntrhy.mirror.aliyuncs.com"]
}
重启服务
systemctl daemon-reload
systemctl restart docker
再次执行hello-world确定是否配置正确
三、docker常用命令
1.帮助启动类命令
systemctl start docker #启动docker
systemctl stop docker #停止docker
systemctl restart docker #重启docker
systemctl status docker #查看docker状态
systemctl enable docker #开机启动
docker info #查看docker概要信息
docker --help #查看docker总体帮助文档
docker 具体指令 --help #查看docker命令帮助文档
2.镜像命令
-
列出本地主机上的镜像：
docker images [OPTIONS]
选项说明：REPOSITORY：表示镜像的仓库源 TAG：镜像的标签版本号（同一镜像源有多个版本） IMAGE ID：镜像ID CREATED：镜像创建时间 SIZE：镜像大小参数说明：
-a #列出本地所有的镜像(含历史映像层) -q #只显示镜像ID -
查找远程仓库中指定镜像：
docker search [OPTIONS] 镜像名字
选项说明：NAME：镜像名称 DESCRIPTION：镜像说明 STARS：点赞数量 OFFICIAL：是否是官方的 AUTOMATED：是否是自动构建的参数说明：
--limit N #只列出N个镜像，默认25个 -
拉取远程仓库中指定的镜像：
docker pull 镜像名字:[TAG版本号]
参数说明：TAG版本号 #可不写，默认为latest，最新 -
查看镜像/容器/数据卷所占空间：
docker system df -
删除镜像：
docker rmi -f 镜像id #删除单个镜像 docker rmi -f 镜像名1:TAG 镜像名2:TAG #删除多个镜像 docker rmi -f 镜像ID1 镜像ID2 #删除多个镜像 docker rmi -f $(docker images -qa) -
什么是虚悬镜像？
虚悬镜像指：仓库名和标签名都是的镜像，俗称虚悬镜像dangling image
建议直接删除该镜像
3.容器命令
-
新建+启动容器：
docker run [OPTIONS] IMAGE [COMMAND] [ARG...]
-it 启动交互式容器docker run -it --name=myu1 ubuntu /bin/bash
-d 启动守护式容器docker run -d --name=myu2 ubuntu(详见下面第5点)
OPTIONS参数说明：--name=容器新名字 #为容器指定新的名称，不写默认随机分配名称 -d #后台运行容器并返回容器ID，即启动守护式容器(后台运行) -i #以交互模式运行容器，通常与-t同时使用 -t #为容器分配一个伪输入终端，通常与-i同时使用 -P #随机指定端口映射，大写P -p #指定端口映射，小写p -
列出当前所有正在运行的容器：
docker ps [OPTIONS]
不加参数表示：展示当前所有正在运行的容器
参数说明：-a # 列出当前所有正在运行的容器+历史上运行过的容器 -l # 显示最近创建的容器 -n X # 显示最近创建的X个容器 -q # 静默模式，只显示容器编号 -
退出容器
exit # run 进去容器，exit退出，容器停止 ctrl+p+q #run 进去容器，ctrl+p+q退出，容器不会停止 -
基础命令
docker start 容器ID或容器名 #启动已经停止运行的容器 docker restart 容器ID或容器名 #重启容器 docker stop 容器ID或容器名 #停止容器 docker kill 容器ID或容器名 #强制停止容器 docker rm 容器ID或容器名 #删除已停止的容器 docker rm -f 容器ID或容器名 #强制删除运行中的容器 #谨慎使用！！！！！！！！！！！！ docker rm -f $(docker ps -qa) 或者 docker ps -qa | xargs docker rm #一次性删除多个容器实例 -
启动守护式容器：
docker run -d --name=myu2 ubuntu后台运行启动失败。因为
docker容器后台运行，必须有一个前台进程，如果不是一直挂起的命令，就是会自动退出的，这是docker的机制。
docker run -d redis后台启动redis
-
查看docker日志：
docker logs 容器ID
-
查看容器内运行的进程：
docker top 容器ID
-
查看容器内部细节：
docker inspect 容器ID
-
进入正在运行中的容器并以命令式交互：
docker exec -it 容器ID /bin/bash（建议使用的方式）
docker attach 容器ID
两种重新进入容器的区别：
>1. attach直接进入容器启动的命令终端，不会启动新的进程，用exit退出，会导致容器停止。
>2. exec是在容器中打开新的终端，并且可以启动新的进程。用exit退出，不会导致容器的停止。
-
从容器内拷贝文件到主机上 ：
docker cp 容器ID:容器内路径 目的主机路径
-
导入和导出容器
-
导出：
docker export 容器ID > 文件名.tar
将容器导出为tar压缩文件
-
导入:
cat 文件名.tar | docker import - 镜像用户/镜像名:镜像版本号
从tar包导入为新的镜像文件，可自定义作者、镜像名和版本号。
-
四、自定义docker镜像
1. 创建本地镜像
docker commit -m="提交的描述信息" -a="作者" 容器ID 要创建的目标镜像名称:标签名
2. 将镜像上传到阿里云镜像仓库
2-1. 创建命名空间
2-2. 创建镜像仓库
2-3. 得到推送和拉取的相关指令
2-4. 执行推送命令
docker login --username=gl龚亮 registry.cn-hangzhou.aliyuncs.com
docker tag [ImageId] registry.cn-hangzhou.aliyuncs.com/gongltest/ubuntuvim:[镜像版本号]
docker push registry.cn-hangzhou.aliyuncs.com/gongltest/ubuntuvim:[镜像版本号]
2-5. 阿里云镜像仓库查看
2-6. 测试拉取
docker pull registry.cn-hangzhou.aliyuncs.com/gongltest/ubuntuvim:[镜像版本号]
3. 将镜像上传到本地私有仓库（docker registry）
3-1.下载镜像docker registry：docker pull registry
3-2. 运行私有库registry，相当于本地有个私有的docker hub：docker run -d -p 5000:5000 -v /zzyyuse/myregistry/:/tmp/registry/ --privileged=true registry
3-3. 创建一个新的镜像，上传到本地私有仓库
3-4. curl验证私有库上有哪些镜像：curl -XGET http://192.168.64.128:5000/v2/_catalog
3-5. 修改新镜像达到私服规范：docker tag 本地镜像名:相应的TAG ip:port/repostry:TAG
3-6. 修改配置文件支持http："insecure-registries":["192.168.64.128:5000"]，注意不要忘记逗号。若修改后不生效，重启docker
3-7. push到私服：docker push 192.168.64.128:5000/gonglubuntu:1.9
3-8. curl验证私有库上有哪些镜像：curl -XGET http://192.168.64.128:5000/v2/_catalog
3-9. pull到本地运行
五、docker 容器数据卷
将容器内的数据持久化到宿主机
docker run -it --privileged=true -v 宿主机的绝对路径:容器内的目录:rw 镜像名
其中：
:rw ：读写权限，可不写，默认也是读写权限。:ro：容器实例内部被限制，只能读
--privileged=true，是权限扩容
-v：要自定义添加容器数据卷
可不加-v参数，默认仓库创建在容器的/var/lib/registry目录下，建议自定义，方便宿主机联调
特点：
- 数据卷可以在容器之间共享或重用数据
- 卷中的更改可以直接实时生效
- 数据卷中的更改不包括在镜像的更新中
- 数据卷的生命周期一直持续到没有容器使用它为止
继承和共享：docker run -it --privileged=true --volumes-from u1 --name=u2 ubuntu
其中的父类指当前容器需要继承的父类的容器名如u1。该方式使宿主机、u1、u2三方实现数据的共享
六、docker常规安装简介
总体步骤：搜索镜像—>拉取镜像—>查看镜像—>启动镜像—>停止容器—>移除容器。
具体版本官网查看地址：https://hub.docker.com/
1. 安装Tomcat
安装最新的tomcat：
docker run -d -p 8080:8080 --name mytomcat tomcat
安装8.0.53版本带jdk8：
docker run -d -p 8080:8080 --name mytomcat8 billygoo/tomcat8-jdk8
访问8080：
2.安装mysql
安装mysql5.7版本：
docker run -d -p 3306:3306 --privileged=true -v /home/mysql/log:/var/log/mysql -v /home/mysql/data:/var/lib/mysql -v /home/mysql/conf:/etc/mysql/conf.d --name=mysql5.7 -e MYSQL_ROOT_PASSWORD=123456 mysql:5.7
my.cnf配置：
[client]
default_character_set=utf8
[mysqld]
collation_server=utf8_general_ci
character_set_server=utf8
docker restart重新加载配置文件
重新进入容器中的mysql查看编码集并添加数据：
Navicat测试：
3. 安装Redis
docker run -d -p 6379:6379 --name myredis --privileged=true -v /app/redis/redis.conf:/etc/redis/redis.conf -v /app/redis/data:/data redis redis-server /etc/redis/redis.conf
-
redis配置文件修改：
daemonize no
#bind 127.0.0.1
protected-mode no
requirepass 123456 -
redis 带密码登录指令：
redis-cli -h 127.0.0.1 -p 6379 -a 123456 -
完整配置文件redis.conf
# Redis configuration file example
# Note on units: when memory size is needed, it is possible to specify
# it in the usual form of 1k 5GB 4M and so forth:
#
# 1k => 1000 bytes
# 1kb => 1024 bytes
# 1m => 1000000 bytes
# 1mb => 1024*1024 bytes
# 1g => 1000000000 bytes
# 1gb => 1024*1024*1024 bytes
#
# units are case insensitive so 1GB 1Gb 1gB are all the same.
################################## INCLUDES ###################################
# Include one or more other config files here. This is useful if you
# have a standard template that goes to all Redis servers but also need
# to customize a few per-server settings. Include files can include
# other files, so use this wisely.
#
# Notice option "include" won't be rewritten by command "CONFIG REWRITE"
# from admin or Redis Sentinel. Since Redis always uses the last processed
# line as value of a configuration directive, you'd better put includes
# at the beginning of this file to avoid overwriting config change at runtime.
#
# If instead you are interested in using includes to override configuration
# options, it is better to use include as the last line.
#
# include .\path\to\local.conf
# include c:\path\to\other.conf
################################## NETWORK #####################################
# By default, if no "bind" configuration directive is specified, Redis listens
# for connections from all the network interfaces available on the server.
# It is possible to listen to just one or multiple selected interfaces using
# the "bind" configuration directive, followed by one or more IP addresses.
#
# Examples:
#
# bind 192.168.1.100 10.0.0.1
# bind 127.0.0.1 ::1
#
# ~~~ WARNING ~~~ If the computer running Redis is directly exposed to the
# internet, binding to all the interfaces is dangerous and will expose the
# instance to everybody on the internet. So by default we uncomment the
# following bind directive, that will force Redis to listen only into
# the IPv4 lookback interface address (this means Redis will be able to
# accept connections only from clients running into the same computer it
# is running).
#
# IF YOU ARE SURE YOU WANT YOUR INSTANCE TO LISTEN TO ALL THE INTERFACES
# JUST COMMENT THE FOLLOWING LINE.
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# bind 127.0.0.1
# Protected mode is a layer of security protection, in order to avoid that
# Redis instances left open on the internet are accessed and exploited.
#
# When protected mode is on and if:
#
# 1) The server is not binding explicitly to a set of addresses using the
# "bind" directive.
# 2) No password is configured.
#
# The server only accepts connections from clients connecting from the
# IPv4 and IPv6 loopback addresses 127.0.0.1 and ::1, and from Unix domain
# sockets.
#
# By default protected mode is enabled. You should disable it only if
# you are sure you want clients from other hosts to connect to Redis
# even if no authentication is configured, nor a specific set of interfaces
# are explicitly listed using the "bind" directive.
protected-mode no
# Accept connections on the specified port, default is 6379 (IANA #815344).
# If port 0 is specified Redis will not listen on a TCP socket.
port 6379
# TCP listen() backlog.
#
# In high requests-per-second environments you need an high backlog in order
# to avoid slow clients connections issues. Note that the Linux kernel
# will silently truncate it to the value of /proc/sys/net/core/somaxconn so
# make sure to raise both the value of somaxconn and tcp_max_syn_backlog
# in order to get the desired effect.
tcp-backlog 511
# Unix socket.
#
# Specify the path for the Unix socket that will be used to listen for
# incoming connections. There is no default, so Redis will not listen
# on a unix socket when not specified.
#
# unixsocket /tmp/redis.sock
# unixsocketperm 700
# Close the connection after a client is idle for N seconds (0 to disable)
timeout 0
# TCP keepalive.
#
# If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
# of communication. This is useful for two reasons:
#
# 1) Detect dead peers.
# 2) Take the connection alive from the point of view of network
# equipment in the middle.
#
# On Linux, the specified value (in seconds) is the period used to send ACKs.
# Note that to close the connection the double of the time is needed.
# On other kernels the period depends on the kernel configuration.
#
# A reasonable value for this option is 60 seconds.
tcp-keepalive 0
################################# GENERAL #####################################
# By default Redis does not run as a daemon. Use 'yes' if you need it.
# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
daemonize yes
# If you run Redis from upstart or systemd, Redis can interact with your
# supervision tree. Options:
# supervised no - no supervision interaction
# supervised upstart - signal upstart by putting Redis into SIGSTOP mode
# supervised systemd - signal systemd by writing READY=1 to $NOTIFY_SOCKET
# supervised auto - detect upstart or systemd method based on
# UPSTART_JOB or NOTIFY_SOCKET environment variables
# Note: these supervision methods only signal "process is ready."
# They do not enable continuous liveness pings back to your supervisor.
# NOT SUPPORTED ON WINDOWS supervised no
# If a pid file is specified, Redis writes it where specified at startup
# and removes it at exit.
#
# When the server runs non daemonized, no pid file is created if none is
# specified in the configuration. When the server is daemonized, the pid file
# is used even if not specified, defaulting to "/var/run/redis.pid".
#
# Creating a pid file is best effort: if Redis is not able to create it
# nothing bad happens, the server will start and run normally.
# NOT SUPPORTED ON WINDOWS pidfile /var/run/redis.pid
# Specify the server verbosity level.
# This can be one of:
# debug (a lot of information, useful for development/testing)
# verbose (many rarely useful info, but not a mess like the debug level)
# notice (moderately verbose, what you want in production probably)
# warning (only very important / critical messages are logged)
loglevel notice
# Specify the log file name. Also 'stdout' can be used to force
# Redis to log on the standard output.
logfile ""
# To enable logging to the Windows EventLog, just set 'syslog-enabled' to
# yes, and optionally update the other syslog parameters to suit your needs.
# If Redis is installed and launched as a Windows Service, this will
# automatically be enabled.
# syslog-enabled no
# Specify the source name of the events in the Windows Application log.
# syslog-ident redis
# Set the number of databases. The default database is DB 0, you can select
# a different one on a per-connection basis using SELECT where
# dbid is a number between 0 and 'databases'-1
databases 16
################################ SNAPSHOTTING ################################
#
# Save the DB on disk:
#
# save
#
# Will save the DB if both the given number of seconds and the given
# number of write operations against the DB occurred.
#
# In the example below the behaviour will be to save:
# after 900 sec (15 min) if at least 1 key changed
# after 300 sec (5 min) if at least 10 keys changed
# after 60 sec if at least 10000 keys changed
#
# Note: you can disable saving completely by commenting out all "save" lines.
#
# It is also possible to remove all the previously configured save
# points by adding a save directive with a single empty string argument
# like in the following example:
#
# save ""
save 900 1
save 300 10
save 60 10000
# By default Redis will stop accepting writes if RDB snapshots are enabled
# (at least one save point) and the latest background save failed.
# This will make the user aware (in a hard way) that data is not persisting
# on disk properly, otherwise chances are that no one will notice and some
# disaster will happen.
#
# If the background saving process will start working again Redis will
# automatically allow writes again.
#
# However if you have setup your proper monitoring of the Redis server
# and persistence, you may want to disable this feature so that Redis will
# continue to work as usual even if there are problems with disk,
# permissions, and so forth.
stop-writes-on-bgsave-error yes
# Compress string objects using LZF when dump .rdb databases?
# For default that's set to 'yes' as it's almost always a win.
# If you want to save some CPU in the saving child set it to 'no' but
# the dataset will likely be bigger if you have compressible values or keys.
rdbcompression yes
# Since version 5 of RDB a CRC64 checksum is placed at the end of the file.
# This makes the format more resistant to corruption but there is a performance
# hit to pay (around 10%) when saving and loading RDB files, so you can disable it
# for maximum performances.
#
# RDB files created with checksum disabled have a checksum of zero that will
# tell the loading code to skip the check.
rdbchecksum yes
# The filename where to dump the DB
dbfilename dump.rdb
# The working directory.
#
# The DB will be written inside this directory, with the filename specified
# above using the 'dbfilename' configuration directive.
#
# The Append Only File will also be created inside this directory.
#
# Note that you must specify a directory here, not a file name.
dir ./
################################# REPLICATION #################################
# Master-Slave replication. Use slaveof to make a Redis instance a copy of
# another Redis server. A few things to understand ASAP about Redis replication.
#
# 1) Redis replication is asynchronous, but you can configure a master to
# stop accepting writes if it appears to be not connected with at least
# a given number of slaves.
# 2) Redis slaves are able to perform a partial resynchronization with the
# master if the replication link is lost for a relatively small amount of
# time. You may want to configure the replication backlog size (see the next
# sections of this file) with a sensible value depending on your needs.
# 3) Replication is automatic and does not need user intervention. After a
# network partition slaves automatically try to reconnect to masters
# and resynchronize with them.
#
# slaveof
# If the master is password protected (using the "requirepass" configuration
# directive below) it is possible to tell the slave to authenticate before
# starting the replication synchronization process, otherwise the master will
# refuse the slave request.
#
# masterauth before processing any other
# commands. This might be useful in environments in which you do not trust
# others with access to the host running redis-server.
#
# This should stay commented out for backward compatibility and because most
# people do not need auth (e.g. they run their own servers).
#
# Warning: since Redis is pretty fast an outside user can try up to
# 150k passwords per second against a good box. This means that you should
# use a very strong password otherwise it will be very easy to break.
#
requirepass 123456
# Command renaming.
#
# It is possible to change the name of dangerous commands in a shared
# environment. For instance the CONFIG command may be renamed into something
# hard to guess so that it will still be available for internal-use tools
# but not available for general clients.
#
# Example:
#
# rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
#
# It is also possible to completely kill a command by renaming it into
# an empty string:
#
# rename-command CONFIG ""
#
# Please note that changing the name of commands that are logged into the
# AOF file or transmitted to slaves may cause problems.
################################### LIMITS ####################################
# Set the max number of connected clients at the same time. By default
# this limit is set to 10000 clients, however if the Redis server is not
# able to configure the process file limit to allow for the specified limit
# the max number of allowed clients is set to the current file limit
# minus 32 (as Redis reserves a few file descriptors for internal uses).
#
# Once the limit is reached Redis will close all the new connections sending
# an error 'max number of clients reached'.
#
# maxclients 10000
# If Redis is to be used as an in-memory-only cache without any kind of
# persistence, then the fork() mechanism used by the background AOF/RDB
# persistence is unnecessary. As an optimization, all persistence can be
# turned off in the Windows version of Redis. This will redirect heap
# allocations to the system heap allocator, and disable commands that would
# otherwise cause fork() operations: BGSAVE and BGREWRITEAOF.
# This flag may not be combined with any of the other flags that configure
# AOF and RDB operations.
# persistence-available [(yes)|no]
# Don't use more memory than the specified amount of bytes.
# When the memory limit is reached Redis will try to remove keys
# according to the eviction policy selected (see maxmemory-policy).
#
# If Redis can't remove keys according to the policy, or if the policy is
# set to 'noeviction', Redis will start to reply with errors to commands
# that would use more memory, like SET, LPUSH, and so on, and will continue
# to reply to read-only commands like GET.
#
# This option is usually useful when using Redis as an LRU cache, or to set
# a hard memory limit for an instance (using the 'noeviction' policy).
#
# WARNING: If you have slaves attached to an instance with maxmemory on,
# the size of the output buffers needed to feed the slaves are subtracted
# from the used memory count, so that network problems / resyncs will
# not trigger a loop where keys are evicted, and in turn the output
# buffer of slaves is full with DELs of keys evicted triggering the deletion
# of more keys, and so forth until the database is completely emptied.
#
# In short... if you have slaves attached it is suggested that you set a lower
# limit for maxmemory so that there is some free RAM on the system for slave
# output buffers (but this is not needed if the policy is 'noeviction').
#
# WARNING: not setting maxmemory will cause Redis to terminate with an
# out-of-memory exception if the heap limit is reached.
#
# NOTE: since Redis uses the system paging file to allocate the heap memory,
# the Working Set memory usage showed by the Windows Task Manager or by other
# tools such as ProcessExplorer will not always be accurate. For example, right
# after a background save of the RDB or the AOF files, the working set value
# may drop significantly. In order to check the correct amount of memory used
# by the redis-server to store the data, use the INFO client command. The INFO
# command shows only the memory used to store the redis data, not the extra
# memory used by the Windows process for its own requirements. Th3 extra amount
# of memory not reported by the INFO command can be calculated subtracting the
# Peak Working Set reported by the Windows Task Manager and the used_memory_peak
# reported by the INFO command.
#
# maxmemory " if needed.
latency-monitor-threshold 0
############################# EVENT NOTIFICATION ##############################
# Redis can notify Pub/Sub clients about events happening in the key space.
# This feature is documented at http://redis.io/topics/notifications
#
# For instance if keyspace events notification is enabled, and a client
# performs a DEL operation on key "foo" stored in the Database 0, two
# messages will be published via Pub/Sub:
#
# PUBLISH __keyspace@0__:foo del
# PUBLISH __keyevent@0__:del foo
#
# It is possible to select the events that Redis will notify among a set
# of classes. Every class is identified by a single character:
#
# K Keyspace events, published with __keyspace@__ prefix.
# E Keyevent events, published with __keyevent@__ prefix.
# g Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
# $ String commands
# l List commands
# s Set commands
# h Hash commands
# z Sorted set commands
# x Expired events (events generated every time a key expires)
# e Evicted events (events generated when a key is evicted for maxmemory)
# A Alias for g$lshzxe, so that the "AKE" string means all the events.
#
# The "notify-keyspace-events" takes as argument a string that is composed
# of zero or multiple characters. The empty string means that notifications
# are disabled.
#
# Example: to enable list and generic events, from the point of view of the
# event name, use:
#
# notify-keyspace-events Elg
#
# Example 2: to get the stream of the expired keys subscribing to channel
# name __keyevent@0__:expired use:
#
# notify-keyspace-events Ex
#
# By default all notifications are disabled because most users don't need
# this feature and the feature has some overhead. Note that if you don't
# specify at least one of K or E, no events will be delivered.
notify-keyspace-events ""
############################### ADVANCED CONFIG ###############################
# Hashes are encoded using a memory efficient data structure when they have a
# small number of entries, and the biggest entry does not exceed a given
# threshold. These thresholds can be configured using the following directives.
hash-max-ziplist-entries 512
hash-max-ziplist-value 64
# Lists are also encoded in a special way to save a lot of space.
# The number of entries allowed per internal list node can be specified
# as a fixed maximum size or a maximum number of elements.
# For a fixed maximum size, use -5 through -1, meaning:
# -5: max size: 64 Kb <-- not recommended for normal workloads
# -4: max size: 32 Kb <-- not recommended
# -3: max size: 16 Kb <-- probably not recommended
# -2: max size: 8 Kb <-- good
# -1: max size: 4 Kb <-- good
# Positive numbers mean store up to _exactly_ that number of elements
# per list node.
# The highest performing option is usually -2 (8 Kb size) or -1 (4 Kb size),
# but if your use case is unique, adjust the settings as necessary.
list-max-ziplist-size -2
# Lists may also be compressed.
# Compress depth is the number of quicklist ziplist nodes from *each* side of
# the list to *exclude* from compression. The head and tail of the list
# are always uncompressed for fast push/pop operations. Settings are:
# 0: disable all list compression
# 1: depth 1 means "don't start compressing until after 1 node into the list,
# going from either the head or tail"
# So: [head]->node->node->...->node->[tail]
# [head], [tail] will always be uncompressed; inner nodes will compress.
# 2: [head]->[next]->node->node->...->node->[prev]->[tail]
# 2 here means: don't compress head or head->next or tail->prev or tail,
# but compress all nodes between them.
# 3: [head]->[next]->[next]->node->node->...->node->[prev]->[prev]->[tail]
# etc.
list-compress-depth 0
# Sets have a special encoding in just one case: when a set is composed
# of just strings that happen to be integers in radix 10 in the range
# of 64 bit signed integers.
# The following configuration setting sets the limit in the size of the
# set in order to use this special memory saving encoding.
set-max-intset-entries 512
# Similarly to hashes and lists, sorted sets are also specially encoded in
# order to save a lot of space. This encoding is only used when the length and
# elements of a sorted set are below the following limits:
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
# HyperLogLog sparse representation bytes limit. The limit includes the
# 16 bytes header. When an HyperLogLog using the sparse representation crosses
# this limit, it is converted into the dense representation.
#
# A value greater than 16000 is totally useless, since at that point the
# dense representation is more memory efficient.
#
# The suggested value is ~ 3000 in order to have the benefits of
# the space efficient encoding without slowing down too much PFADD,
# which is O(N) with the sparse encoding. The value can be raised to
# ~ 10000 when CPU is not a concern, but space is, and the data set is
# composed of many HyperLogLogs with cardinality in the 0 - 15000 range.
hll-sparse-max-bytes 3000
# Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
# order to help rehashing the main Redis hash table (the one mapping top-level
# keys to values). The hash table implementation Redis uses (see dict.c)
# performs a lazy rehashing: the more operation you run into a hash table
# that is rehashing, the more rehashing "steps" are performed, so if the
# server is idle the rehashing is never complete and some more memory is used
# by the hash table.
#
# The default is to use this millisecond 10 times every second in order to
# actively rehash the main dictionaries, freeing memory when possible.
#
# If unsure:
# use "activerehashing no" if you have hard latency requirements and it is
# not a good thing in your environment that Redis can reply from time to time
# to queries with 2 milliseconds delay.
#
# use "activerehashing yes" if you don't have such hard requirements but
# want to free memory asap when possible.
activerehashing yes
# The client output buffer limits can be used to force disconnection of clients
# that are not reading data from the server fast enough for some reason (a
# common reason is that a Pub/Sub client can't consume messages as fast as the
# publisher can produce them).
#
# The limit can be set differently for the three different classes of clients:
#
# normal -> normal clients including MONITOR clients
# slave -> slave clients
# pubsub -> clients subscribed to at least one pubsub channel or pattern
#
# The syntax of every client-output-buffer-limit directive is the following:
#
# client-output-buffer-limit
#
# A client is immediately disconnected once the hard limit is reached, or if
# the soft limit is reached and remains reached for the specified number of
# seconds (continuously).
# So for instance if the hard limit is 32 megabytes and the soft limit is
# 16 megabytes / 10 seconds, the client will get disconnected immediately
# if the size of the output buffers reach 32 megabytes, but will also get
# disconnected if the client reaches 16 megabytes and continuously overcomes
# the limit for 10 seconds.
#
# By default normal clients are not limited because they don't receive data
# without asking (in a push way), but just after a request, so only
# asynchronous clients may create a scenario where data is requested faster
# than it can read.
#
# Instead there is a default limit for pubsub and slave clients, since
# subscribers and slaves receive data in a push fashion.
#
# Both the hard or the soft limit can be disabled by setting them to zero.
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit slave 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
# Redis calls an internal function to perform many background tasks, like
# closing connections of clients in timeot, purging expired keys that are
# never requested, and so forth.
#
# Not all tasks are perforemd with the same frequency, but Redis checks for
# tasks to perform according to the specified "hz" value.
#
# By default "hz" is set to 10. Raising the value will use more CPU when
# Redis is idle, but at the same time will make Redis more responsive when
# there are many keys expiring at the same time, and timeouts may be
# handled with more precision.
#
# The range is between 1 and 500, however a value over 100 is usually not
# a good idea. Most users should use the default of 10 and raise this up to
# 100 only in environments where very low latency is required.
hz 10
# When a child rewrites the AOF file, if the following option is enabled
# the file will be fsync-ed every 32 MB of data generated. This is useful
# in order to commit the file to the disk more incrementally and avoid
# big latency spikes.
aof-rewrite-incremental-fsync yes
################################## INCLUDES ###################################
# Include one or more other config files here. This is useful if you
# have a standard template that goes to all Redis server but also need
# to customize a few per-server settings. Include files can include
# other files, so use this wisely.
#
# include /path/to/local.conf
# include /path/to/other.conf