new article docker --progress=plain

Author: pymongo

2021/12/async_cancel_propagation.md

@@ -67,12 +67,12 @@ index 5226249b..6de7f682 100644
 
 ```
 Dec 18 10:39:21 ww systemd[715]: Stopping graph...
-Dec 18 10:39:21 ww atlasd[1518986]: 2021-12-18 10:39:21.588323  INFO atlasd: Signal SIGTERM received, stopping this daemon server
-Dec 18 10:39:21 ww atlasd[1518986]: 2021-12-18 10:39:21.588408  INFO server::graph: Prepare to stop graph server
-Dec 18 10:39:21 ww atlasd[1518986]: 2021-12-18 10:39:21.588744  INFO start_prometheus_exporter{ip=0.0.0.0 port=19100 instance_kind=Graph}:prometheus_exporter(accept): common::metrics::prome>
-Dec 18 10:39:21 ww atlasd[1518986]: 2021-12-18 10:39:21.588830  INFO web::server: graceful shutdown web server
+Dec 18 10:39:21 ww appd[1518986]: 2021-12-18 10:39:21.588323  INFO appd: Signal SIGTERM received, stopping this daemon server
+Dec 18 10:39:21 ww appd[1518986]: 2021-12-18 10:39:21.588408  INFO server::graph: Prepare to stop graph server
+Dec 18 10:39:21 ww appd[1518986]: 2021-12-18 10:39:21.588744  INFO start_prometheus_exporter{ip=0.0.0.0 port=19100 instance_kind=Graph}:prometheus_exporter(accept): common::metrics::prome>
+Dec 18 10:39:21 ww appd[1518986]: 2021-12-18 10:39:21.588830  INFO web::server: graceful shutdown web server
 Dec 18 10:40:51 ww systemd[715]: graph.service: State 'stop-sigterm' timed out. Killing.
-Dec 18 10:40:51 ww systemd[715]: graph.service: Killing process 1518986 (atlasd) with signal SIGKILL.
+Dec 18 10:40:51 ww systemd[715]: graph.service: Killing process 1518986 (appd) with signal SIGKILL.
 Dec 18 10:40:51 ww systemd[715]: graph.service: Killing process 1518988 (tokio-runtime-w) with signal SIGKILL.
 Dec 18 10:40:51 ww systemd[715]: graph.service: Killing process 1518989 (tokio-runtime-w) with signal SIGKILL.
 Dec 18 10:40:51 ww systemd[715]: graph.service: Killing process 1518993 (tokio-runtime-w) with signal SIGKILL.

2021/12/cargo_tree_invert.md

@@ -57,18 +57,18 @@ openssl-sys v0.9.72
 ├── native-tls v0.2.8
 │   ├── hyper-tls v0.5.0
 │   │   └── reqwest v0.11.7
-│   │       └── web v0.1.0 (/home/w/repos/haizhi/atlas/src/web)
-│   │           └── server v0.1.0 (/home/w/repos/haizhi/atlas/src/server)
+│   │       └── web v0.1.0 (/home/w/repos/company/app/src/web)
+│   │           └── server v0.1.0 (/home/w/repos/company/app/src/server)
 │   │       [dev-dependencies]
-│   │       └── web v0.1.0 (/home/w/repos/haizhi/atlas/src/web) (*)
+│   │       └── web v0.1.0 (/home/w/repos/company/app/src/web) (*)
 │   ├── reqwest v0.11.7 (*)
 │   └── tokio-native-tls v0.3.0
 │       ├── hyper-tls v0.5.0 (*)
 │       └── reqwest v0.11.7 (*)
 └── openssl v0.10.38
     ├── native-tls v0.2.8 (*)
     └── osshkeys v0.5.2
-        ├── common v0.1.0 (/home/w/repos/haizhi/atlas/src/common)
+        ├── common v0.1.0 (/home/w/repos/company/app/src/common)
 ...
 ```
 

2022/07/docker_build_progress_plain.md

@@ -0,0 +1,14 @@
+# [docker --progress=plain](/2022/07/docker_build_progress_plain.md)
+
+自从启用 buildkit 之后 docker build 的进度条就变成固定高度滚动更新的内容
+
+```
+cat /etc/docker/daemon.json
+{
+    "features": { "buildkit": true }
+}
+```
+
+导致运行到 STEP 6 的时候看不到 STEP 5 的 stdout，没开 buildkit 的时候 dockerfile 代码会打成白色而 stdout/stderr 打成红色
+
+今天才发现 docker build 加上 **--progress=plain** 参数可以保留所有 STEP 的所有输出

2022/07/docker_container_core_dumped_illegal_instruction.md

@@ -1,4 +1,4 @@
-# [container illegal instr](/2022/07/docker_container_core_dumped_illegal_instruction.md)
+# [docker illegal instr](/2022/07/docker_container_core_dumped_illegal_instruction.md)
 
 ```
 https://twitter.com/ospopen/status/1544970889925885952
@@ -11,6 +11,9 @@ illegal instruction (core dumped)
 看来还是高版本 glibc 编译出来的可执行文件不能在低版本系统运行的限制
 ```
 
+但我觉得是 fedora:36 的 glibc 2.35 发生了一些不兼容改动吧，
+毕竟公司生产服务器上宿主机 centos7 常年跑 centos8/ubuntu:20.04 的应用也没问题
+
 容器内没有捕获 coredump 的话，coredump 会记录在宿主机的 dmesg
 
 ```

README.md

@@ -1,6 +1,7 @@
 - [文章列表 - 吴翱翔的博客](/)
 - **2022-07**
-    - [container illegal instr](/2022/07/docker_container_core_dumped_illegal_instruction.md)
+    - [docker --progress=plain](/2022/07/docker_build_progress_plain.md)
+    - [docker illegal instr](/2022/07/docker_container_core_dumped_illegal_instruction.md)
 - **2022-06**
     - [arch pip TypeError](/2022/06/arch_pip_fail_after_system_upgrade.md)
     - [/bin/timeout](/2022/06/bin_timeout.md)