search

limnh / journey

Notes and learnings along the way of becoming an engineer
0 stars 1 forks source link

2019-03-12 #18

Open limnh opened 5 years ago

limnh commented 5 years ago

Issues/Questions:

  1. have run into a myriad of issues with getting scp to work properly.

    • the build image job was put into its own block as follows: apk update && apk add jq export PACKET_IP=$(terraform output -json address | jq .value.address |sed -e 's/"//g') echo $PACKET_IP scp shell.sh ubuntu.json root@$PACKET_IP:/tmp ssh -o StrictHostKeyChecking=no root@$PACKET_IP 'curl https://releases.hashicorp.com/packer/1.3.5/packer_1.3.5_linux_amd64.zip -o packer.zip && apt-get update && apt-get install unzip && unzip packer.zip -d /usr/bin && packer version && ls -la /tmp' The module root could not be found. There is nothing to output. ssh: Could not resolve hostname :Name does not resolve. lost connection
    • CircleCI normally defaults to $HOME/project for cloning files. however, this isn't searchable (and I don't know why yet).

  2. how do we get the qemu image to the cloud?

Solutions:

  1. shit's still borked

    • initially, we believed it was necessary to cd ../../../../ to reach the correct level for scp to work, but this may be unnecessary.
    • cleaned up the build image step by breaking it out and making it more readable

  2. checked in with SME, they recommended using awscli instead of vagrant cloud due to dependencies that would make the process more complex