谷歌雲啟動腳本未運行

Question

啟動腳本的行為與我預期的不同。

我在存儲桶中有一個.sh文件，並且包含一個startup-script-url元標記，其值為gs://bucket-name/start-script.sh

[[0;32m  OK  [0m] Started Google Compute Engine Accounts Daemon.
         Starting Google Compute Engine Startup Scripts...
[[0;32m  OK  [0m] Started Google Compute Engine Shutdown Scripts.
[[0;32m  OK  [0m] Started Google Compute Engine Startup Scripts.
[[0;32m  OK  [0m] Started Docker Application Container Engine.
[[0;32m  OK  [0m] Started Wait for Google Container Registry (GCR) to be accessible.
[[0;32m  OK  [0m] Reached target Google Container Registry (GCR) is Online.
[[0;32m  OK  [0m] Started Containers on GCE Setup.
[    8.001248] konlet-startup[1018]: 2018/03/08 20:23:56 Starting Konlet container startup agent

以下腳本未按預期執行。 我嘗試使用startup-script元數據標記並使用類似echo "hello"的簡單內容，但這也不起作用。 我啟用了完整的 Cloud API 訪問范圍。

如果我復制以下文件的內容並將其粘貼到 ssh 終端中，它可以完美運行。

真的可以使用一些幫助=D

啟動腳本.sh

#! /bin/bash

image_name=gcr.io/some-image:version-2
docker_images=$(docker inspect --type=image $image_name)
array_count=${#docker_images[0]}

# Check if docker image is available
while ((array_count = 2));
do
    docker_images=$(docker inspect --type=image ${image_name})
    array_count=${#docker_images[0]}

    if (($array_count > 2)); then
        break
    fi
done

################################
#
#   Docker image now injected
#   by google compute engine
#
################################

echo "docker image ${image_name} available"

container_ids=($(docker container ls | grep ${image_name} | awk '{ print $1}'))

for (( i=0; i < ${#container_ids[@]}; i++ ));
do
    # run command for each container
    container_id=${container_ids[i]}
    echo "running commands for container: ${container_ids[i]}"

    # start cloud sql proxy
    docker container run -d -p $HOST_PORT:$APPLICATION_PORT \
    ${container_ids[i]} \
    ./cloud_sql_proxy \
    -instances=$PG_INSTANCE_CONNECTION_NAME=tcp:$PG_PORT \
    -credential_file=$PG_CREDENTIAL_FILE_LOCATION

    # HTTP - Start unicorn webserver
    docker exec -d \
    ${container_ids[i]} \
    bundle exec unicorn -c config/unicorn.rb
done

Answer 1

啟動腳本的行為不像我期望的那樣。

我在存儲桶中有一個.sh文件，並且包含了一個值為gs://bucket-name/start-script.sh的startup-script-url元標記

[[0;32m  OK  [0m] Started Google Compute Engine Accounts Daemon.
         Starting Google Compute Engine Startup Scripts...
[[0;32m  OK  [0m] Started Google Compute Engine Shutdown Scripts.
[[0;32m  OK  [0m] Started Google Compute Engine Startup Scripts.
[[0;32m  OK  [0m] Started Docker Application Container Engine.
[[0;32m  OK  [0m] Started Wait for Google Container Registry (GCR) to be accessible.
[[0;32m  OK  [0m] Reached target Google Container Registry (GCR) is Online.
[[0;32m  OK  [0m] Started Containers on GCE Setup.
[    8.001248] konlet-startup[1018]: 2018/03/08 20:23:56 Starting Konlet container startup agent

以下腳本未按預期執行。 我嘗試使用startup-script元數據標簽並使用像echo "hello"這樣簡單的東西，但這也不起作用。 我啟用了完整的 Cloud API 訪問范圍。

如果我復制以下文件的內容並將其粘貼到 ssh 終端中，它將完美運行。

真的可以使用一些幫助 =D

啟動腳本.sh

#! /bin/bash

image_name=gcr.io/some-image:version-2
docker_images=$(docker inspect --type=image $image_name)
array_count=${#docker_images[0]}

# Check if docker image is available
while ((array_count = 2));
do
    docker_images=$(docker inspect --type=image ${image_name})
    array_count=${#docker_images[0]}

    if (($array_count > 2)); then
        break
    fi
done

################################
#
#   Docker image now injected
#   by google compute engine
#
################################

echo "docker image ${image_name} available"

container_ids=($(docker container ls | grep ${image_name} | awk '{ print $1}'))

for (( i=0; i < ${#container_ids[@]}; i++ ));
do
    # run command for each container
    container_id=${container_ids[i]}
    echo "running commands for container: ${container_ids[i]}"

    # start cloud sql proxy
    docker container run -d -p $HOST_PORT:$APPLICATION_PORT \
    ${container_ids[i]} \
    ./cloud_sql_proxy \
    -instances=$PG_INSTANCE_CONNECTION_NAME=tcp:$PG_PORT \
    -credential_file=$PG_CREDENTIAL_FILE_LOCATION

    # HTTP - Start unicorn webserver
    docker exec -d \
    ${container_ids[i]} \
    bundle exec unicorn -c config/unicorn.rb
done

Answer 2

啟動腳本的行為不像我期望的那樣。

我在存儲桶中有一個.sh文件，並且包含了一個值為gs://bucket-name/start-script.sh的startup-script-url元標記

[[0;32m  OK  [0m] Started Google Compute Engine Accounts Daemon.
         Starting Google Compute Engine Startup Scripts...
[[0;32m  OK  [0m] Started Google Compute Engine Shutdown Scripts.
[[0;32m  OK  [0m] Started Google Compute Engine Startup Scripts.
[[0;32m  OK  [0m] Started Docker Application Container Engine.
[[0;32m  OK  [0m] Started Wait for Google Container Registry (GCR) to be accessible.
[[0;32m  OK  [0m] Reached target Google Container Registry (GCR) is Online.
[[0;32m  OK  [0m] Started Containers on GCE Setup.
[    8.001248] konlet-startup[1018]: 2018/03/08 20:23:56 Starting Konlet container startup agent

以下腳本未按預期執行。 我嘗試使用startup-script元數據標簽並使用像echo "hello"這樣簡單的東西，但這也不起作用。 我啟用了完整的 Cloud API 訪問范圍。

如果我復制以下文件的內容並將其粘貼到 ssh 終端中，它將完美運行。

真的可以使用一些幫助 =D

啟動腳本.sh

#! /bin/bash

image_name=gcr.io/some-image:version-2
docker_images=$(docker inspect --type=image $image_name)
array_count=${#docker_images[0]}

# Check if docker image is available
while ((array_count = 2));
do
    docker_images=$(docker inspect --type=image ${image_name})
    array_count=${#docker_images[0]}

    if (($array_count > 2)); then
        break
    fi
done

################################
#
#   Docker image now injected
#   by google compute engine
#
################################

echo "docker image ${image_name} available"

container_ids=($(docker container ls | grep ${image_name} | awk '{ print $1}'))

for (( i=0; i < ${#container_ids[@]}; i++ ));
do
    # run command for each container
    container_id=${container_ids[i]}
    echo "running commands for container: ${container_ids[i]}"

    # start cloud sql proxy
    docker container run -d -p $HOST_PORT:$APPLICATION_PORT \
    ${container_ids[i]} \
    ./cloud_sql_proxy \
    -instances=$PG_INSTANCE_CONNECTION_NAME=tcp:$PG_PORT \
    -credential_file=$PG_CREDENTIAL_FILE_LOCATION

    # HTTP - Start unicorn webserver
    docker exec -d \
    ${container_ids[i]} \
    bundle exec unicorn -c config/unicorn.rb
done

Answer 3

在從 /tmp 中刪除文件的執行權限后，我遇到了類似的問題。 考慮到啟動腳本被復制到 /tmp/ 然后從那里運行。

Answer 4

Container-Optimized OS 的啟動腳本必須以不同方式配置。 使用user-data元數據標簽，並將其傳遞給 cloud-config 配置。 文檔中的示例如下。

#cloud-config

bootcmd:
- fsck.ext4 -tvy /dev/DEVICE_ID
- mkdir -p /mnt/disks/MNT_DIR
- mount -t ext4 -O ... /dev/DEVICE_ID /mnt/disks/MNT_DIR