DevOps Community Sponsored by Cloud Posse

SweetOps

im a geodesic noob. how does one run it ?

```docker run -it cloudposse/geodesic
docker run -it cloudposse/geodesic bash```
both fail

Oh, so when you run it with no arguments it outputs a bash script installer 

The result is a script is installed that helps you start it since running long Docker commands is no fun 


If you just want to kick the tires and skip installation, then add -l 

ah ok now it works. ya i just wanted to try it out


```docker run -it cloudposse/geodesic -l```
 

The way we use it is as a base Docker image for our customers 

We like to mount $HOME to /localhost so we can access files during development (e.g. tf)

you dont mount it to /conf the root `$HOME` ?

```docker run -v "$HOME:/localhost" -it cloudposse/geodesic -l```


Conf is where we copy the configurations for distribution in the Docker file that is FROM geodesic 

<https://github.com/cloudposse/packages/tree/master/vendor|https://github.com/cloudposse/packages/tree/master/vendor>

All of these tools are easily installed. We update every night automatically 

hmmm

```⨠ aws-vault exec sso_sre --server
Enter passphrase to unlock /conf/.awsvault/keys/:
Enter passphrase to unlock /conf/.awsvault/keys/:
Enter passphrase to unlock /conf/.awsvault/keys/:
aws-vault: error: exec: fork/exec : no such file or directory```


thanks for the help. i'll keep playing with it

ya i was trying to use the same profiles i have setup locally

i can see my profiles when doing `aws-vault list`

So I think you need to use the vault backend of file for it to work across OS barriers 

Used
```docker run --env AWS_VAULT_BACKEND=file -v "$HOME:/localhost" -it cloudposse/geodesic -l```
then
```⨠ env | grep AWS_VAULT
AWS_VAULT_SERVER_ENABLED=false
AWS_VAULT_BACKEND=file
AWS_VAULT_ENABLED=false
 ⧉  geodesic
 √ . [default] ~ ⨠ aws-vault exec sso_sre --server
Enter passphrase to unlock /conf/.awsvault/keys/:
aws-vault: error: exec: fork/exec : no such file or directory```


this seems to work tho

```aws-vault exec sso_sre -- aws sts get-caller-identity
Enter passphrase to unlock /conf/.awsvault/keys/:

{
    "UserId": "snip",
    "Account": "snip",
    "Arn": "snip"
}```


```aws-vault exec --server sso_sre -- /bin/bash -l```
