App Service Linux におけるコンテナ起動ログが変わった

# はじめに

この記事はログから確認できた情報に基づいて記載しています。
2024年03月12日時点で、西日本リージョンのリソースで確認しています。

# 以前のログに関する参考記事

https://azure.github.io/jpazpaas/2023/07/27/AppServiceOnLinux-Log.html#%E3%83%AD%E3%82%B0%E4%BE%8B

https://qiita.com/georgeOsdDev@github/items/abdadd35248b98c4ef88#%E5%AE%9F%E9%9A%9B%E3%81%AB%E5%88%A9%E7%94%A8%E3%81%95%E3%82%8C%E3%82%8B%E3%82%B3%E3%83%B3%E3%83%86%E3%83%8A%E3%82%A4%E3%83%A1%E3%83%BC%E3%82%B8blessed-image

# コンテナ起動ログ

## 以前のログ(東日本リソースより)

こんな感じで `docker run` してる様子が見れました。

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/4914/c2e7dda8-99be-9984-0aac-d358c0e6c440.png)


```2024_03_11_lw1sdlwk0000R5_docker.log
2024-03-11T19:26:14.533Z INFO  - Starting container for site
2024-03-11T19:26:14.538Z INFO  - docker run -d --expose=8080 --name toshida-linux-node_10_ffe1046d -e WEBSITE_USE_DIAGNOSTIC_SERVER=true -e WEBSITE_AUTH_ENABLED=False -e WEBSITE_SITE_NAME=toshida-linux-node -e PORT=8080 -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=toshida-linux-node.azurewebsites.net -e WEBSITE_INSTANCE_ID=b08b793703ed90c29d190499db3bc194822d9b232329810c8844678e66822c18 -e HTTP_LOGGING_ENABLED=1 -e NODE_OPTIONS=--require /agents/nodejs/build/src/Loader.js appsvc/node:20-lts_20240207.3.tuxprod 
2024-03-11T19:26:27.097Z INFO  - Initiating warmup request to container toshida-linux-node_10_ffe1046d_msiProxy for site toshida-linux-node
2024-03-11T19:26:27.329Z INFO  - Container toshida-linux-node_10_ffe1046d_msiProxy for site toshida-linux-node initialized successfully and is ready to serve requests.
2024-03-11T19:26:27.330Z INFO  - Initiating warmup request to container toshida-linux-node_10_ffe1046d for site toshida-linux-node
2024-03-11T19:27:05.885Z INFO  - Waiting for response to warmup request for container toshida-linux-node_10_ffe1046d. Elapsed time = 38.8005835 sec
2024-03-11T19:27:25.702Z INFO  - Waiting for response to warmup request for container toshida-linux-node_10_ffe1046d. Elapsed time = 58.6233176 sec
2024-03-11T19:27:43.829Z INFO  - Container toshida-linux-node_10_ffe1046d for site toshida-linux-node initialized successfully and is ready to serve requests.
2024-03-11T19:27:43.841Z INFO  - Initiating warmup request to container toshida-linux-node_10_ffe1046d_middleware for site toshida-linux-node
2024-03-11T19:27:48.228Z INFO  - Container toshida-linux-node_10_ffe1046d_middleware for site toshida-linux-node initialized successfully and is ready to serve requests.
```

## 今回西日本のリソースで確認できた起動ログ

`docker run` や warmup のログが見られなくなりました。

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/4914/5097177c-8797-b64b-0b01-33bfcc940dbb.png)

```2024_03_11_lw0sdlwk0003AP_docker.log
2024-03-11T21:24:35.6150916Z Container start method called.
2024-03-11T21:24:36.0369435Z Establishing network.
2024-03-11T21:24:36.0466787Z Pulling image: mcr.microsoft.com/appsvc/node:20-lts_20240207.3.tuxprod.
2024-03-11T21:25:45.4294659Z Container is starting.
2024-03-11T21:25:45.4383743Z Establishing network if not established already.
2024-03-11T21:25:45.4404137Z Mounting volumes.
2024-03-11T21:25:45.4495663Z Nested mountpoint 
2024-03-11T21:25:45.4862088Z Nested mountpoint volatile/logs
2024-03-11T21:25:45.5075529Z Nested mountpoint 
2024-03-11T21:25:45.6408068Z Nested mountpoint 
2024-03-11T21:26:04.6502818Z Creating container.
2024-03-11T21:26:04.6714930Z Creating pipes for streaming container io.
2024-03-11T21:26:04.6797169Z Creating stdout named pipe at /podr/container/pipe/202403-linux-app-jw_ed541221/stdout_7f76ac9c16d54b739db5b626511a81d9.
2024-03-11T21:26:04.6817893Z Successfully created stdout named pipe at: /podr/container/pipe/202403-linux-app-jw_ed541221/stdout_7f76ac9c16d54b739db5b626511a81d9.
2024-03-11T21:26:04.6990803Z Opening named pipe /podr/container/pipe/202403-linux-app-jw_ed541221/stdout_7f76ac9c16d54b739db5b626511a81d9 for reading in non-blocking mode.
2024-03-11T21:26:04.7011427Z Successfully opened named pipe: /podr/container/pipe/202403-linux-app-jw_ed541221/stdout_7f76ac9c16d54b739db5b626511a81d9.
2024-03-11T21:26:04.7271397Z Successfully removed non-blocking flag from /podr/container/pipe/202403-linux-app-jw_ed541221/stdout_7f76ac9c16d54b739db5b626511a81d9.
2024-03-11T21:26:04.7290739Z Creating stderr named pipe at /podr/container/pipe/202403-linux-app-jw_ed541221/stderr_398a5c56ea0c4d7fbeb12a6986a8c927.
2024-03-11T21:26:04.7370767Z Successfully created stderr named pipe at: /podr/container/pipe/202403-linux-app-jw_ed541221/stderr_398a5c56ea0c4d7fbeb12a6986a8c927.
2024-03-11T21:26:04.7388397Z Opening named pipe /podr/container/pipe/202403-linux-app-jw_ed541221/stderr_398a5c56ea0c4d7fbeb12a6986a8c927 for reading in non-blocking mode.
2024-03-11T21:26:04.7470220Z Successfully opened named pipe: /podr/container/pipe/202403-linux-app-jw_ed541221/stderr_398a5c56ea0c4d7fbeb12a6986a8c927.
2024-03-11T21:26:04.7491165Z Successfully removed non-blocking flag from /podr/container/pipe/202403-linux-app-jw_ed541221/stderr_398a5c56ea0c4d7fbeb12a6986a8c927.
2024-03-11T21:26:05.3676293Z Starting container: 202403-linux-app-jw_ed541221.
2024-03-11T21:26:05.7350909Z Starting watchers and probes.
2024-03-11T21:26:05.7555614Z Starting metrics collection.
2024-03-11T21:26:05.7638076Z Container is running.
2024-03-11T21:26:05.9502478Z Container start method finished after 89941 ms.
2024-03-11T21:29:49.9410242Z Container start method called.
2024-03-11T21:29:50.0787118Z Establishing network.
2024-03-11T21:29:50.0882005Z Pulling image: mcr.microsoft.com/appsvc/kudulite:bookworm_20240207.2.tuxprod.
2024-03-11T21:29:51.6542908Z Container is starting.
2024-03-11T21:29:51.6637735Z Establishing network if not established already.
2024-03-11T21:29:51.6732880Z Mounting volumes.
2024-03-11T21:29:51.7392180Z Nested mountpoint 
2024-03-11T21:29:51.7709669Z Nested mountpoint volatile/logs
2024-03-11T21:29:51.7888095Z Nested mountpoint 
2024-03-11T21:29:51.8967469Z Nested mountpoint 
2024-03-11T21:29:51.9360545Z Nested mountpoint 
2024-03-11T21:29:52.0258572Z Creating container.
2024-03-11T21:29:52.0350845Z Creating pipes for streaming container io.
2024-03-11T21:29:52.0442193Z Creating stdout named pipe at /podr/container/pipe/202403-linux-app-jw_kudu_9d2e8a06/stdout_e517a313a8ee45be9d37b7267455a77e.
2024-03-11T21:29:52.0476262Z Successfully created stdout named pipe at: /podr/container/pipe/202403-linux-app-jw_kudu_9d2e8a06/stdout_e517a313a8ee45be9d37b7267455a77e.
2024-03-11T21:29:52.0636508Z Opening named pipe /podr/container/pipe/202403-linux-app-jw_kudu_9d2e8a06/stdout_e517a313a8ee45be9d37b7267455a77e for reading in non-blocking mode.
2024-03-11T21:29:52.0659364Z Successfully opened named pipe: /podr/container/pipe/202403-linux-app-jw_kudu_9d2e8a06/stdout_e517a313a8ee45be9d37b7267455a77e.
2024-03-11T21:29:52.0766512Z Successfully removed non-blocking flag from /podr/container/pipe/202403-linux-app-jw_kudu_9d2e8a06/stdout_e517a313a8ee45be9d37b7267455a77e.
2024-03-11T21:29:52.0858472Z Creating stderr named pipe at /podr/container/pipe/202403-linux-app-jw_kudu_9d2e8a06/stderr_e45904e671c74b2192e1be1c81e3f44e.
2024-03-11T21:29:52.0943809Z Successfully created stderr named pipe at: /podr/container/pipe/202403-linux-app-jw_kudu_9d2e8a06/stderr_e45904e671c74b2192e1be1c81e3f44e.
2024-03-11T21:29:52.1023382Z Opening named pipe /podr/container/pipe/202403-linux-app-jw_kudu_9d2e8a06/stderr_e45904e671c74b2192e1be1c81e3f44e for reading in non-blocking mode.
2024-03-11T21:29:52.1126082Z Successfully opened named pipe: /podr/container/pipe/202403-linux-app-jw_kudu_9d2e8a06/stderr_e45904e671c74b2192e1be1c81e3f44e.
2024-03-11T21:29:52.1234214Z Successfully removed non-blocking flag from /podr/container/pipe/202403-linux-app-jw_kudu_9d2e8a06/stderr_e45904e671c74b2192e1be1c81e3f44e.
2024-03-11T21:29:52.7043415Z Starting container: 202403-linux-app-jw_kudu_9d2e8a06.
2024-03-11T21:29:52.8822792Z Starting watchers and probes.
2024-03-11T21:29:52.9028698Z Starting metrics collection.
2024-03-11T21:29:52.9117551Z Container is running.
2024-03-11T21:29:53.0197500Z Container start method finished after 2950 ms.
```

# scm(Kudu)コンテナのログ

`YYYY_MM_DD_<HostName>_default_scm_docker.log` というファイルが出力されるようになっていました。Kudu コンテナの標準出力が残るようです。

![image.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/4914/ea870da4-a51f-262a-6cd5-f6fc81bb6231.png)

# その他

この変更が↓のようなサイドカーパターンの実現につながるのか。

https://techcommunity.microsoft.com/t5/apps-on-azure-blog/a-glimpse-into-the-future-the-sidecar-pattern-on-linux-app/ba-p/4045680