一、离线安装docker

1、下载离线包

https://link.zhihu.com/?target=https%3A//download.docker.com/linux/static/stable/x86_64/

docker-18.09.8.tgz

2、安装docker

复制docker-18.09.8.tgz到 /usr/bin下（usr/bin是环境变量目录，在路径下可以直接运行docker命令）

解压

tar xvf docker-18.09.8.tgz

ls -l docker

cp docker/* /usr/bin

rm -rf docker docker-18.09.8.tgz

配置docker服务

vim /etc/systemd/system/docker.service

添加

[Unit]

Description=Docker Application Container Engine

Documentation=https://docs.docker.com

After=network-online.target firewalld.service

Wants=network-online.target

[Service]

Type=notify

ExecStart=/usr/bin/dockerd

ExecReload=/bin/kill -s HUP $MAINPID

LimitNOFILE=infinity

LimitNPROC=infinity

TimeoutStartSec=0

Delegate=yes

KillMode=process

Restart=on-failure

StartLimitBurst=3

StartLimitInterval=60s

[Install]

WantedBy=multi-user.target

赋执行权限

chmod +x /etc/systemd/system/docker.service

systemctl daemon-reload

3. docker 命令

开机启动

systemctl enable docker.service

启动docker

systemctl start docker

docker状态

systemctl status docker

重启docker服务

systemctl restart docker

二、docker-compose 离线安装

1. 下载离线包

下载离线包

https://github.com/docker/compose/releases

下载的最新版本（这里要展开才能看到）

docker-compose-linux-x86_64

2. 安装docker-compose

上传安装包

改名为docker-compose 复制到 /usr/local/bin/下

cp -f ./docker-compose-linux-x86_64 /usr/local/bin/docker-compose

赋执行权限

chmod +x /usr/local/bin/docker-compose

三、 docker 离线镜像

1、在有网络的环境下下载镜像

redis 镜像

docker pull redis:5.0.14

2、导出镜像

docker save redis:5.0.14 -o redis5014.tar

2、上传离线环境导入镜像

docker load -i redis5014.tar

3、查看镜像

docker images

4、创建redis管理目录，方便后期管理

mkdir data

5、编辑redis.conf配置文件

vim redis.conf

Redis configuration file example.

#

 # Note that in order to read the configuration file, Redis must be

 # started with the file path as first argument:

 #

 # ./redis-server /path/to/redis.conf

 ​

 # 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 /path/to/other.conf

 ​

 ################################## MODULES #####################################

 ​

 # Load modules at startup. If the server is not able to load modules

 # it will abort. It is possible to use multiple loadmodule directives.

 #

 # loadmodule /path/to/my_module.so

 # loadmodule /path/to/other_module.so

 ​

 ################################## 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 300 seconds, which is the new

 # Redis default starting with Redis 3.2.1.

 tcp-keepalive 300

 ​

 ################################# 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.

 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.

 pidfile /var/run/redis_6379.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 the empty string can be used to force

 # Redis to log on the standard output. Note that if you use standard

 # output for logging but daemonize, logs will be sent to /dev/null

 logfile “”

 ​

 # To enable logging to the system logger, just set ‘syslog-enabled’ to yes,

 # and optionally update the other syslog parameters to suit your needs.

 # syslog-enabled no

 ​

 # Specify the syslog identity.

 # syslog-ident redis

 ​

 # Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.

 # syslog-facility local0

 ​

 # 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

 ​

 # By default Redis shows an ASCII art logo only when started to log to the

 # standard output and if the standard output is a TTY. Basically this means

 # that normally a logo is displayed only in interactive sessions.

 #

 # However it is possible to force the pre-4.0 behavior and always show a

 # ASCII art logo in startup logs by setting the following option to yes.

 always-show-logo yes

 ​

 ################################ 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

 ​

 # When a slave loses its connection with the master, or when the replication

 # is still in progress, the slave can act in two different ways:

 #

 # 1) if slave-serve-stale-data is set to ‘yes’ (the default) the slave will

 #    still reply to client requests, possibly with out of date data, or the

 #    data set may just be empty if this is the first synchronization.

 #

 # 2) if slave-serve-stale-data is set to ‘no’ the slave will reply with

 #    an error “SYNC with master in progress” to all the kind of commands

 #    but to INFO and SLAVEOF.

 #

 slave-serve-stale-data yes

 ​

 # You can configure a slave instance to accept writes or not. Writing against

 # a slave instance may be useful to store some ephemeral data (because data

 # written on a slave will be easily deleted after resync with the master) but

 # may also cause problems if clients are writing to it because of a

 # misconfiguration.

 #

 # Since Redis 2.6 by default slaves are read-only.

 #

 # Note: read only slaves are not designed to be exposed to untrusted clients

 # on the internet. It’s just a protection layer against misuse of the instance.

 # Still a read only slave exports by default all the administrative commands

 # such as CONFIG, DEBUG, and so forth. To a limited extent you can improve

 # security of read only slaves using ‘rename-command’ to shadow all the

 # administrative / dangerous commands.

 slave-read-only yes

 ​

 # Replication SYNC strategy: disk or socket.

 #

 # -------------------------------------------------------

 # WARNING: DISKLESS REPLICATION IS EXPERIMENTAL CURRENTLY

 # -------------------------------------------------------

 #

 # New slaves and reconnecting slaves that are not able to continue the replication

 # process just receiving differences, need to do what is called a “full

 # synchronization”. An RDB file is transmitted from the master to the slaves.

 # The transmission can happen in two different ways:

 #

 # 1) Disk-backed: The Redis master creates a new process that writes the RDB

 #                 file on disk. Later the file is transferred by the parent

 #                 process to the slaves incrementally.

 # 2) Diskless: The Redis master creates a new process that directly writes the

 #              RDB file to slave sockets, without touching the disk at all.

 #

 # With disk-backed replication, while the RDB file is generated, more slaves

 # can be queued and served with the RDB file as soon as the current child producing

 # the RDB file finishes its work. With diskless replication instead once

 # the transfer starts, new slaves arriving will be queued and a new transfer

 # will start when the current one terminates.

 #

 # When diskless replication is used, the master waits a configurable amount of

 # time (in seconds) before starting the transfer in the hope that multiple slaves

 # will arrive and the transfer can be parallelized.

 #

 # With slow disks and fast (large bandwidth) networks, diskless replication

 # works better.

 repl-diskless-sync no

 ​

 # When diskless replication is enabled, it is possible to configure the delay

 # the server waits in order to spawn the child that transfers the RDB via socket

 # to the slaves.

 #

 # This is important since once the transfer starts, it is not possible to serve

 # new slaves arriving, that will be queued for the next RDB transfer, so the server

 # waits a delay in order to let more slaves arrive.

 #

 # The delay is specified in seconds, and by default is 5 seconds. To disable

 # it entirely just set it to 0 seconds and the transfer will start ASAP.

 repl-diskless-sync-delay 5

 ​

 # Slaves send PINGs to server in a predefined interval. It’s possible to change

 # this interval with the repl_ping_slave_period option. The default value is 10

 # seconds.

 #

 # repl-ping-slave-period 10

 ​

 # The following option sets the replication timeout for:

 #

 # 1) Bulk transfer I/O during SYNC, from the point of view of slave.

 # 2) Master timeout from the point of view of slaves (data, pings).

 # 3) Slave timeout from the point of view of masters (REPLCONF ACK pings).

 #

 # It is important to make sure that this value is greater than the value

 # specified for repl-ping-slave-period otherwise a timeout will be detected

 # every time there is low traffic between the master and the slave.

 #

 # repl-timeout 60

 ​

 # Disable TCP_NODELAY on the slave socket after SYNC?

 #

 # If you select “yes” Redis will use a smaller number of TCP packets and

 # less bandwidth to send data to slaves. But this can add a delay for

 # the data to appear on the slave side, up to 40 milliseconds with

 # Linux kernels using a default configuration.

 #

 # If you select “no” the delay for data to appear on the slave side will

 # be reduced but more bandwidth will be used for replication.

 #

 # By default we optimize for low latency, but in very high traffic conditions

 # or when the master and slaves are many hops away, turning this to “yes” may

 # be a good idea.

 repl-disable-tcp-nodelay no

 ​

 # Set the replication backlog size. The backlog is a buffer that accumulates

 # slave data when slaves are disconnected for some time, so that when a slave

 # wants to reconnect again, often a full resync is not needed, but a partial

 # resync is enough, just passing the portion of data the slave missed while

 # disconnected.

 #

 # The bigger the replication backlog, the longer the time the slave can be

 # disconnected and later be able to perform a partial resynchronization.

 #

 # The backlog is only allocated once there is at least a slave connected.

 #

 # repl-backlog-size 1mb

 ​

 # After a master has no longer connected slaves for some time, the backlog

 # will be freed. The following option configures the amount of seconds that

 # need to elapse, starting from the time the last slave disconnected, for

 # the backlog buffer to be freed.

 #

 # Note that slaves never free the backlog for timeout, since they may be

 # promoted to masters later, and should be able to correctly “partially

 # resynchronize” with the slaves: hence they should always accumulate backlog.

 #

 # A value of 0 means to never release the backlog.

 #

 # repl-backlog-ttl 3600

 ​

 # The slave priority is an integer number published by Redis in the INFO output.

 # It is used by Redis Sentinel in order to select a slave to promote into a

 # master if the master is no longer working correctly.

 #

 # A slave with a low priority number is considered better for promotion, so

 # for instance if there are three slaves with priority 10, 100, 25 Sentinel will

 # pick the one with priority 10, that is the lowest.

 #

 # However a special priority of 0 marks the slave as not able to perform the

 # role of master, so a slave with priority of 0 will never be selected by

 # Redis Sentinel for promotion.

 #

 # By default the priority is 100.

 slave-priority 100

 ​

 # It is possible for a master to stop accepting writes if there are less than

 # N slaves connected, having a lag less or equal than M seconds.

 #

 # The N slaves need to be in “online” state.

 #

 # The lag in seconds, that must be <= the specified value, is calculated from

 # the last ping received from the slave, that is usually sent every second.

 #

 # This option does not GUARANTEE that N replicas will accept the write, but

 # will limit the window of exposure for lost writes in case not enough slaves

 # are available, to the specified number of seconds.

 #

 # For example to require at least 3 slaves with a lag <= 10 seconds use:

 #

 # min-slaves-to-write 3

 # min-slaves-max-lag 10

 #

 # Setting one or the other to 0 disables the feature.

 #

 # By default min-slaves-to-write is set to 0 (feature disabled) and

 # min-slaves-max-lag is set to 10.

 ​

 # A Redis master is able to list the address and port of the attached

 # slaves in different ways. For example the “INFO replication” section

 # offers this information, which is used, among other tools, by

 # Redis Sentinel in order to discover slave instances.

 # Another place where this info is available is in the output of the

 # “ROLE” command of a master.

 #

 # The listed IP and address normally reported by a slave is obtained

in the following way:

#

IP: The address is auto detected by checking the peer address

of the socket used by the slave to connect with the master.

#

Port: The port is communicated by the slave during the replication

handshake, and is normally the port that the slave is using to

list for connections.

#

However when port forwarding or Network Address Translation (NAT) is

used, the slave may be actually reachable via different IP and port

pairs. The following two options can be used by a slave in order to

report to its master a specific set of IP and port, so that both INFO

and ROLE will report those values.

#

There is no need to use both the options if you need to override just

the port or the IP address.

#

slave-announce-ip 5.5.5.5

slave-announce-port 1234

​ 

################################## SECURITY ################################### 

​

Require clients to issue AUTH 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 foobared

​

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.

​ 

################################### CLIENTS #################################### 

​

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

​ 

############################## MEMORY MANAGEMENT ################################ 

​

Set a memory usage limit to 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 or LFU 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’).

#

maxmemory

​

MAXMEMORY POLICY: how Redis will select what to remove when maxmemory

is reached. You can select among five behaviors:

#

volatile-lru -> Evict using approximated LRU among the keys with an expire set.

allkeys-lru -> Evict any key using approximated LRU.

volatile-lfu -> Evict using approximated LFU among the keys with an expire set.

allkeys-lfu -> Evict any key using approximated LFU.

volatile-random -> Remove a random key among the ones with an expire set.

allkeys-random -> Remove a random key, any key.

volatile-ttl -> Remove the key with the nearest expire time (minor TTL)

noeviction -> Don’t evict anything, just return an error on write operations.

#

自我介绍一下，小编13年上海交大毕业，曾经在小公司待过，也去过华为、OPPO等大厂，18年进入阿里一直到现在。

深知大多数Linux运维工程师，想要提升技能，往往是自己摸索成长或者是报班学习，但对于培训机构动则几千的学费，着实压力不小。自己不成体系的自学效果低效又漫长，而且极易碰到天花板技术停滞不前！

因此收集整理了一份《2024年Linux运维全套学习资料》，初衷也很简单，就是希望能够帮助到想自学提升又不知道该从何学起的朋友，同时减轻大家的负担。

既有适合小白学习的零基础资料，也有适合3年以上经验的小伙伴深入学习提升的进阶课程，基本涵盖了95%以上Linux运维知识点，真正体系化！

由于文件比较大，这里只是将部分目录大纲截图出来，每个节点里面都包含大厂面经、学习笔记、源码讲义、实战项目、讲解视频，并且后续会持续更新

如果你觉得这些内容对你有帮助，可以添加VX：vip1024b （备注Linux运维获取）

为了做好运维面试路上的助攻手，特整理了上百道 【运维技术栈面试题集锦】 ，让你面试不慌心不跳，高薪offer怀里抱！

这次整理的面试题，小到shell、MySQL，大到K8s等云原生技术栈，不仅适合运维新人入行面试需要，还适用于想提升进阶跳槽加薪的运维朋友。

本份面试集锦涵盖了

174 道运维工程师面试题128道k8s面试题108道shell脚本面试题200道Linux面试题51道docker面试题35道Jenkis面试题78道MongoDB面试题17道ansible面试题60道dubbo面试题53道kafka面试18道mysql面试题40道nginx面试题77道redis面试题28道zookeeper

总计 1000+ 道面试题， 内容 又全含金量又高

174道运维工程师面试题

1、什么是运维?

2、在工作中，运维人员经常需要跟运营人员打交道，请问运营人员是做什么工作的?

3、现在给你三百台服务器，你怎么对他们进行管理?

4、简述raid0 raid1raid5二种工作模式的工作原理及特点

5、LVS、Nginx、HAproxy有什么区别?工作中你怎么选择?

6、Squid、Varinsh和Nginx有什么区别，工作中你怎么选择?

7、Tomcat和Resin有什么区别，工作中你怎么选择?

8、什么是中间件?什么是jdk?

9、讲述一下Tomcat8005、8009、8080三个端口的含义？

10、什么叫CDN?

11、什么叫网站灰度发布?

12、简述DNS进行域名解析的过程?

13、RabbitMQ是什么东西?

14、讲一下Keepalived的工作原理?

15、讲述一下LVS三种模式的工作过程?

16、mysql的innodb如何定位锁问题，mysql如何减少主从复制延迟?

17、如何重置mysql root密码?

一个人可以走的很快，但一群人才能走的更远。如果你从事以下工作或对以下感兴趣，欢迎戳这里加入程序员的圈子，让我们一起学习成长！

AI人工智能、Android移动开发、AIGC大模型、C C#、Go语言、Java、Linux运维、云计算、MySQL、PMP、网络安全、Python爬虫、UE5、UI设计、Unity3D、Web前端开发、产品经理、车载开发、大数据、鸿蒙、计算机网络、嵌入式物联网、软件测试、数据结构与算法、音视频开发、Flutter、IOS开发、PHP开发、.NET、安卓逆向、云计算

面试题**

77道redis面试题28道zookeeper

总计 1000+ 道面试题， 内容 又全含金量又高

174道运维工程师面试题

1、什么是运维?

2、在工作中，运维人员经常需要跟运营人员打交道，请问运营人员是做什么工作的?

3、现在给你三百台服务器，你怎么对他们进行管理?

4、简述raid0 raid1raid5二种工作模式的工作原理及特点

5、LVS、Nginx、HAproxy有什么区别?工作中你怎么选择?

6、Squid、Varinsh和Nginx有什么区别，工作中你怎么选择?

7、Tomcat和Resin有什么区别，工作中你怎么选择?

8、什么是中间件?什么是jdk?

9、讲述一下Tomcat8005、8009、8080三个端口的含义？

10、什么叫CDN?

11、什么叫网站灰度发布?

12、简述DNS进行域名解析的过程?

13、RabbitMQ是什么东西?

14、讲一下Keepalived的工作原理?

15、讲述一下LVS三种模式的工作过程?

16、mysql的innodb如何定位锁问题，mysql如何减少主从复制延迟?

17、如何重置mysql root密码?

一个人可以走的很快，但一群人才能走的更远。如果你从事以下工作或对以下感兴趣，欢迎戳这里加入程序员的圈子，让我们一起学习成长！

AI人工智能、Android移动开发、AIGC大模型、C C#、Go语言、Java、Linux运维、云计算、MySQL、PMP、网络安全、Python爬虫、UE5、UI设计、Unity3D、Web前端开发、产品经理、车载开发、大数据、鸿蒙、计算机网络、嵌入式物联网、软件测试、数据结构与算法、音视频开发、Flutter、IOS开发、PHP开发、.NET、安卓逆向、云计算