solo-io / unik

The Unikernel & MicroVM Compilation and Deployment Platform
Apache License 2.0
2.72k stars 191 forks source link

AWS build never completes / no errors reported #128

Closed tedonmain closed 7 years ago

tedonmain commented 7 years ago

MacOS: 10.12.4 Virtual Box: 5.1.20r114629 Go 1.8.1 AWS CLI installed with full Administrator

build command in root Go folder $ unik build --name myGoImage --path ./ --base rump --language go --provider aws

no errors are indicated but the command prompt never returns after several hours.

Each time a new EBS volume is created on AWS and also a new S3 bucket is created which contains named disk image

No indication of success of any kind issuing $ unik instances

**daemon-config.yaml: providers: aws:

I have followed the examples provided in docs here exactly several times. I repeated 5 times on AWS and each time the result was a new EBS volume and a new S3 bucket with the image.

Note: deploying locally --provider virtualbox works great (awesome stuff!) except unik instances command does not refresh showing IP address and current state (just continues to show pending) of instances. I have to guess the local IP assigned by DHCP. Otherwise local deploy to virtualbox works just fine. Wondering hot to get AWS working the same.

Thanks!

AustinAske commented 7 years ago

I am having the same issue with the following daemon output repeating forever: DEBU[0204] request sent to ec2 params={ ConversionTaskIds: ["import-vol-#######"] }

Thanks!