-
-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux support (including new-user documentation) #139
Comments
This is priceless feedback! I update the docs (tomorrow) and work with you to get it sorted out. |
I'm going to take a stab at answering some of these inline. Let me just say that we know the docs are woefully incomplete, but we're investing hundreds of hours into them right now.
I think we will be updating the |
This is actually due to running |
We have a pretty good write up on how we use this. @goruha uses linux too, so it's working pretty well. The key is to use Our docs for |
I think we can loosen this requirement so that it only applies to OSX. The original reason is for OSX so we can run |
100% agree. This has been surprisingly difficult to get right from a documentation perspective. Hope by EOW this will be in better shape. |
Okay, so I think the first thing is to think about "infrastructure code" the same as any other application code that you would ship with docker. For example, if you were going to distribute a NodeJS app, you'd distribute the
For example, here's what one of our typical
So as you can see from the above examples, we don't "mount" (per say) the Now, since rebuilding the container during development would be extremely tedious, we do mount |
The bigger question is how to deal with terraform remote state, if you're not doing it our way. We have some bad docs on how we do it. They are bad in that they are the "complicated" way that can be simplified. Not yet sure when I can get to simplifying it, but the best thing is if we do a quick call this week or if you ping @aknysh on |
Also, want to link to https://github.com/cloudposse/terraform-aws-tfstate-backend which is our module for managing tfstate. We use this little helper script ( |
I know |
Per what docs? Neither the geodesic Readme nor the docs site mentioned
installation.
…On Sat, Jun 2, 2018, 10:54 PM Erik Osterman ***@***.***> wrote:
This is actually due to running docker run -it; the -it causes it to run
in "interactive tty mode" which causes the \r new line endings. Per the
docs, drop the -it =)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#139 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AfNDKMaVir7vxVCAFj4DYmG9adM-euyYks5t40_tgaJpZM4UXoxQ>
.
|
My apologies. It does appear that that got lost somewhere. I'll be updating the |
We've improved linux support but still have problems with permissions on mounted directories. We've also added support for WSL (windows). https://docs.cloudposse.com/documentation/getting-started/ |
This isn't a bug-report per-se but a new-user feedback list and items that would be needed to complete the documentation:
docker run --rm -it $IMAGE | tr -d "\r" > $TMP && bash $TMP 0.9.17
--privileged
? If it's a must, then this complicates using aws-vault in both geodesic and native (geodesic will create vault keys as root in your home directory)The text was updated successfully, but these errors were encountered: