-
Notifications
You must be signed in to change notification settings - Fork 56
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
Windows amd64/ia64 local gcloud client support: terraform apply via ming64/git-bash tested - expected win32 issue running bootstrap module check_env.sh works only inside docker container (ubuntu or google/cloud-sdk) - or use cloud shell #429
Comments
reproducing on oldev
terraform plan
|
run terraform from git-bashexpected until adjust the path
install
micha@p1gen6 MINGW64 ~
|
run terraform plan in git-bash/ming64
login first
terraform plan
|
terraform docker container via rebuilt for amd64 imagehttps://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/blob/gh399-ado/build/docker/build.sh
Need local directory set
I'll need a vm or persistent container - as rerunning the terraform executable is not preserving state |
Switch to base ubuntu image - or gcloud-slim, add terraform - run as headless container - mount 0-bootstrap dirtesting before gcloud/terraform retrofit of DockerFile
|
https://hub.docker.com/r/google/cloud-sdk/https://hub.docker.com/r/google/cloud-sdk/
manually add terraform before modifying the DockerFilehttps://releases.hashicorp.com/terraform/1.3.10/
terraform plan in the container
gcloud auth application-default login
ok the container still complaining about win32 even though we are in a linux container
Issue is symlinks up above current dir needs to be flattened first - or the shared dir moved up one to retest |
rerun docker container in root directory above 0-bootstraphistory
shutdown / restart container
same think at the root dir - missing provider dir checking whether there is a conflict between terraform binary and .terraform dir
should not be
|
run the repo inside the container - emulating cloud shell
|
run terraform from root dir - clone inside docker container
works inside container - with terraform outside the current directorycheck on shared drive
run on shared dir
keep the repo inside the container - and copy out the plan and state files after |
fix
|
An example of an attempted gcloud csr clone will kick in the authentication dialog
Client after re-authentication " move to #431 |
. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Fix: run google/cloud-sdk docker container, install terraform, clone repo inside container - move plan/statefile out via -v separate shared dir to host
Issue
First time a 2nd party user ran the LZ from an AVD windows vm
step 4 of https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/tree/main/0-bootstrap#deploying-with-cloud-build
specifically sh on windows.
Quick fix - run ming64 and watch symlinks on #428
Reproduction: I will run the LZ from my Lenovo P1Gen6 and document in
https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/wiki/DevOps#local-windows
from client
see https://registry.terraform.io/modules/terraform-google-modules/bootstrap/google/latest
for example in my last run on cloud shell (unix) we were ok in #360
The following is during apply where the sh scripts would eventually fail as well.
Reproducing in
https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/wiki/DevOps#local-windows
triage
and
terraform-google-modules/terraform-google-cloud-operations#13
The text was updated successfully, but these errors were encountered: