Score:0

Google cloudd VM instance kills docker

vn flag

I have cloud vm instance e2-medium that runs my docker container. Certain activity at docker container causes CPU spike, like up to 140% out of 200%. I guess that OS kills docker, I see this entry at VM logs:

MESSAGE: "2023-03-06T20:32:57.227924026Z container kill 5572d73a11cb38164529d1c1b284bce64e7b1f559ef4946c28e24a68d4b9e706 (image=gcr.io/stackdriver-agents/stackdriver-logging-agent:1.9.8, name=stackdriver-logging-agent, signal=23)"

_STREAM_ID: "a728b1d527b844efaf47948fd4ab78ec"
SYSLOG_FACILITY: "3"
_SYSTEMD_SLICE: "system.slice"
_GID: "0"
_SYSTEMD_INVOCATION_ID: "e74c20509740491e9f029fc0a0705c06"
_CAP_EFFECTIVE: "1ffffffffff"
SYSLOG_IDENTIFIER: "docker"
_UID: "0"
_EXE: "/usr/bin/docker"
PRIORITY: "6"
_SYSTEMD_UNIT: "docker-events-collector.service"
_PID: "418"
_BOOT_ID: "5056c013dda44eebbd7ff5548718b430"
_MACHINE_ID: "25b3ce0a5d18787ea1ef8aae1f78278e"
_HOSTNAME: "cloud-search-agent-03"
_SYSTEMD_CGROUP: "/system.slice/docker-events-collector.service"
_CMDLINE: "/usr/bin/docker events"
_COMM: "docker"

Is there any possibility to prevent it? BTW, why does monitoring show CPU utilisation but doesn't have memory utilisation chart?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.