BusyBox 是一个集成了一百多个最常用 Linux 命令和工具(如 cat、echo、grep、mount、telnet 、ping、ifconfig 等)的精简工具箱,它只需要几 MB 的大小,很方便进行各种快速验证,被誉为“Linux 系统的瑞士军刀”。
1
docker run --name box1 -it --rm busybox sh
–rm 在退出容器时自动销毁该容器
docker compose 修改yml后更新容器
参考Docker Compose更新容器的几种方法 如果已经修改了docker-compose.yml文件,并且希望更新其中的某个容器,可以直接使用docker-compose up -d命令。该命令会更新docker-compose.yml中修改过的服务,并根据修改的设置进行重新配置。例如:
1
docker-compose up -d service-name
其中 service-name是需要更新的服务名。
dokcer 根据container 生成image
1 2 3 4 5 6 7 8 9 10 11 12 13
第一种方法:使用commit
//查看所有的容器 docker container ls -a //suspicious_mcnulty是原容器name,gmk/centos-vim是新image的REPOSITORY docker commit centos bivana/centos-env //查看新镜像 docker image ls
docker push bivana/centos-env
docker 宿主机和容器拷贝文件
1
docker cp 本地路径 容器id或者容器名字:容器内路径
Failed to get D-Bus connection: Operation not permitted
docker 里的centos 如果要运行 systemctl 命令,需要以特权模式运行容器
1
docker run -d --name centos --privileged=true centos:7 /usr/sbin/init
PS C:\Users\dell> docker network ls NETWORK ID NAME DRIVER SCOPE 415ecf186909 bridge bridge local b01f87d53a20 dw-network macvlan local 0ec71466bed7 host host local 417fdf60fc8c nonenulllocal
启动容器并绑定固定ip
1 2 3 4 5 6 7 8 9
docker run --net=dw-network --name="test1" --ip=172.16.1.11 -e MYSQL_ROOT_PASSWORD=root -d mysql:8.0.33 docker run --net=dw-network --name="test2" --ip=172.16.1.12 -e MYSQL_ROOT_PASSWORD=root -d mysql:8.0.33
查看容器 docker ps -a 可以看到有两个容器已经启动 CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 569bb77f586e mysql:8.0.33 "docker-entrypoint.s…" 4 seconds ago Up 2 seconds test2 224b3db441ae mysql:8.0.33 "docker-entrypoint.s…" 30 seconds ago Up 29 seconds test1
INFO Start processing INFO Files loaded in 2.58 s INFO 0 files generated in 3.25 s INFO Deploying: rsync 'rsync' is not recognized as an internal or external command, operable program or batch file. FATAL { err: Error: spawn rsync ENOENT at notFoundError (D:\git\personal\test_blog\node_modules\cross-spawn\lib\enoent.js:6:26) at verifyENOENT (D:\git\personal\test_blog\node_modules\cross-spawn\lib\enoent.js:40:16) at cp.emit (D:\git\personal\test_blog\node_modules\cross-spawn\lib\enoent.js:27:25) at ChildProcess._handle.onexit (node:internal/child_process:291:12) { code: 'ENOENT', errno: 'ENOENT', syscall: 'spawn rsync', path: 'rsync', spawnargs: [ '--delete', '--ignore-errors', '-v', '-az', '-e', 'D:\\soft\\install\\cwrsync_6.2.8_x64_free\\bin\\ssh -p 22', 'public/', 'root@www.test.com:/www/test_blog' ] } } Something's wrong. Maybe you can find the solution here: %s https://hexo.io/docs/troubleshooting.html
‘rsync’ is not recognized as an internal or external command
其实这个错误说的挺明显的了,rsync无法识别,于是搜索windows hexo 'rsync' is not recognized as an internal or external command,得到了使用Hexo发布博客(Windows环境),了解到windows系统默认没有rsync,因此需要下载安装。
INFO Start processing INFO Files loaded in 2.19 s INFO 0 files generated in 3.11 s INFO Deploying: rsync root@www.test.com's password: rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.2] rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(231) [sender=3.2.7] FATAL { err: Error: rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.2] rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(231) [sender=3.2.7] at ChildProcess.<anonymous> (D:\git\personal\test_blog\node_modules\hexo-deployer-rsync\node_modules\hexo-util\lib\spawn.js:36:19) at ChildProcess.emit (node:events:513:28) at cp.emit (D:\git\personal\test_blog\node_modules\cross-spawn\lib\enoent.js:34:29) at maybeClose (node:internal/child_process:1091:16) at ChildProcess._handle.onexit (node:internal/child_process:302:5) { code: 12 } } Something's wrong. Maybe you can find the solution here: %s https://hexo.io/docs/troubleshooting.html
err: Error: rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
于是网上搜索 hexo windows err: Error: rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] 搜到了Cygwin 使用rsync 报错解决这篇文章,经过验证后,确认是因为rsync 的ssh和系统默认的ssh冲突导致的,具体原因这里就不深入了。
由于rsync实际要调用ssh,而在调用ssh时,系统的open ssh优先,实际调用了open ssh,没有调用到rsync自带的ssh,导致版本错配,进而发生了rsync error: error in rsync protocol data stream (code 12) at io.c(231)这个异常。
INFO Start processing INFO Files loaded in 2.58 s INFO 0 files generated in 3.9 s INFO Deploying: rsync Host key verification failed. rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(231) [sender=3.2.7] FATAL { err: Error: Host key verification failed. rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(231) [sender=3.2.7]
at ChildProcess.<anonymous> (D:\git\personal\test_blog\node_modules\hexo-deployer-rsync\node_modules\hexo-util\lib\spawn.js:36:19) at ChildProcess.emit (node:events:513:28) at cp.emit (D:\git\personal\test_blog\node_modules\cross-spawn\lib\enoent.js:34:29) at maybeClose (node:internal/child_process:1091:16) at ChildProcess._handle.onexit (node:internal/child_process:302:5) { code: 12 } } Something's wrong. Maybe you can find the solution here: %s https://hexo.io/docs/troubleshooting.html
INFO Start processing INFO Files loaded in 2.1 s INFO 0 files generated in 3.04 s INFO Deploying: rsync Permission denied, please try again. Permission denied, please try again. root@www.test.com: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(231) [sender=3.2.7] FATAL { err: Error: Permission denied, please try again. Permission denied, please try again. root@www.test.com: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(231) [sender=3.2.7]
at ChildProcess.<anonymous> (D:\git\personal\test_blog\node_modules\hexo-deployer-rsync\node_modules\hexo-util\lib\spawn.js:36:19) at ChildProcess.emit (node:events:513:28) at cp.emit (D:\git\personal\test_blog\node_modules\cross-spawn\lib\enoent.js:34:29) at maybeClose (node:internal/child_process:1091:16) at ChildProcess._handle.onexit (node:internal/child_process:302:5) { code: 12 } } Something's wrong. Maybe you can find the solution here: %s https://hexo.io/docs/troubleshooting.html
修改前 if (args.verbose) params.unshift('-v'); if (args.ignore_errors) params.unshift('--ignore-errors'); if (args.delete) params.unshift('--delete'); if (args.args) params.unshift(args.args); 修改后 params.unshift('--chmod=ugo=rx'); if (args.verbose) params.unshift('-v'); if (args.ignore_errors) params.unshift('--ignore-errors'); if (args.delete) params.unshift('--delete'); if (args.args) params.unshift(args.args);
PS C:/Users/ivan/AppData/Local/Programs/Python/Python311/python tjj_hgsj_py/nj_tjj.py Traceback (most recent call last): File"tjj_hgsj_py\nj_tjj.py", line 20, in <module> tables= camelot.read_pdf(pdfFilePath)####从1开始计数 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File"C:\Users\ivan\AppData\Local\Programs\Python\Python311\Lib\site-packages\camelot\io.py", line 113, in read_pdf tables = p.parse( ^^^^^^^^ File"C:\Users\ivan\AppData\Local\Programs\Python\Python311\Lib\site-packages\camelot\handlers.py", line 176, in parse t = parser.extract_tables( ^^^^^^^^^^^^^^^^^^^^^^ File"C:\Users\ivan\AppData\Local\Programs\Python\Python311\Lib\site-packages\camelot\parsers\lattice.py", line 421, in extract_tables self.backend.convert(self.filename, self.imagename) File"C:\Users\ivan\AppData\Local\Programs\Python\Python311\Lib\site-packages\camelot\backends\ghostscript_backend.py", line 36, in convert import ghostscript ModuleNotFoundError: No module named 'ghostscript'
Welcome to Hexo! This is your very first post. Check documentation for more info. If you get any problems when using Hexo, you can find the answer in troubleshooting or you can ask me on GitHub.