繁体 English 中英

使用 Githubactions/Terraform 通过 SSH 连接 EC2 时没有这样的主机？

[英]No such host when connecting EC2 through SSH using Githubactions/Terraform?

原文 2022-12-21 04:57:31 4 0 amazon-ec2/ terraform/ github-actions

2022/12/22 07:23:13 拨打 tcp：查找“ec2-XX-XXX-XXX-XXX.compute-1.amazonaws.com”：没有这样的主机

我也尝试过使用 IP 地址和 DNS 命名两者..相同的行为

但它在 AWS 中可用，我可以通过 Putty 进行连接。 当我在 cmd 提示中 ping Ip 时，它是可达的。

当尝试从 github 操作连接时，我们看到没有主机错误

我从通过 aws 生成并在 github 秘密中给出的 pem 文件中获取了私钥。

我创建了 C:\Users{myname}.ssh 文件夹。 在该文件下添加了一个文件 authorized_keys 并添加了通过 (ssh-keygen -y -f vpcpublickey.pem > vpcpublickey.pub) 获得的公钥

还缺少什么？ 任何人都可以看看吗？ 那真的很有帮助。

Run appleboy/ssh-action@master
  with:
    host: "ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com"
    username: ec2-user
    key: ***
    port: 22
    script: sudo yum update -y
  sudo yum install docker -y
  sudo service docker start
  sudo usermod -a -G docker ec2-user
  sudo su docker pull ***/newdocker:v2
  sudo su docker run  -p 80:3000 ***/newdocker:v2
  
    sync: false
    use_insecure_cipher: false
    timeout: 30s
    command_timeout: 10m
    proxy_port: 22
    proxy_timeout: 30s
    proxy_use_insecure_cipher: false
    script_stop: false
    debug: false
  env:
    SERVER_PUBLIC_IP: ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com
    AWS_DEFAULT_REGION: us-east-1
    AWS_REGION: ***
    AWS_ACCESS_KEY_ID: ***
    AWS_SECRET_ACCESS_KEY: ***
/usr/bin/docker run --name dd213c4d116b4aab9178cc1249c92d79_9e2022 --label 290506 --workdir /github/workspace --rm -e "SERVER_PUBLIC_IP" -e "AWS_DEFAULT_REGION" -e "AWS_REGION" -e "AWS_ACCESS_KEY_ID" -e "AWS_SECRET_ACCESS_KEY" -e "INPUT_HOST" -e "INPUT_USERNAME" -e "INPUT_KEY" -e "INPUT_PORT" -e "INPUT_SCRIPT" -e "INPUT_PASSPHRASE" -e "INPUT_PASSWORD" -e "INPUT_SYNC" -e "INPUT_USE_INSECURE_CIPHER" -e "INPUT_CIPHER" -e "INPUT_TIMEOUT" -e "INPUT_COMMAND_TIMEOUT" -e "INPUT_KEY_PATH" -e "INPUT_FINGERPRINT" -e "INPUT_PROXY_HOST" -e "INPUT_PROXY_PORT" -e "INPUT_PROXY_USERNAME" -e "INPUT_PROXY_PASSWORD" -e "INPUT_PROXY_PASSPHRASE" -e "INPUT_PROXY_TIMEOUT" -e "INPUT_PROXY_KEY" -e "INPUT_PROXY_KEY_PATH" -e "INPUT_PROXY_FINGERPRINT" -e "INPUT_PROXY_CIPHER" -e "INPUT_PROXY_USE_INSECURE_CIPHER" -e "INPUT_SCRIPT_STOP" -e "INPUT_ENVS" -e "INPUT_DEBUG" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/UserManagement/UserManagement":"/github/workspace" 290506:dd213c4d116b4aab9178cc1249c92d79
2022/12/22 07:23:13 dial tcp: lookup "ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com": no such host
======CMD======
sudo yum update -y
sudo yum install docker -y
sudo service docker start
sudo usermod -a -G docker ec2-user
sudo su docker pull ***/newdocker:v2
sudo su docker run  -p 80:3000 ***/newdocker:v2