cloud engineer
If you have SSSD running and the default shell is ksh even with the default shell set to bash.
Here’s the fix to override the default shell in /etc/sssd/sssd.conf. Add override_shell.
default_shell = /bin/bash override_shell = /bin/bash |
default_shell = /bin/bash override_shell = /bin/bash
To check which shell you are using.
echo $SHELL /bin/bash |
echo $SHELL /bin/bash
Here’s how to move a VM to another network.
Stop the VM.
gcloud compute instances stop server-name \ --zone=us-central1-c \ --project project-id |
gcloud compute instances stop server-name \ --zone=us-central1-c \ --project project-id
Migrate the VM. Use self link for network and subnetwork.
gcloud compute instances network-interfaces update server-name \ --zone=us-central1-c \ --network-interface=nic0 \ --network=your-network \ --subnetwork=your-sub-network \ --project project-id |
gcloud compute instances network-interfaces update server-name \ --zone=us-central1-c \ --network-interface=nic0 \ --network=your-network \ --subnetwork=your-sub-network \ --project project-id
Start the VM.
gcloud compute instances start server-name \ --zone=us-central1-c \ --project project-id |
gcloud compute instances start server-name \ --zone=us-central1-c \ --project project-id
There are a few issues that prop up every once in a while with gcloud compute ssh. gcloud compute ssh creates local user at first login. The account password has a default expiration of 90 days. If unable to login, you can try logging in as a different name (even a fictitious name) e.g. superheroes, etc. something unique.
gcloud compute ssh username@servername --zone us-central1-c --project project-id --internal-ip |
gcloud compute ssh username@servername --zone us-central1-c --project project-id --internal-ip
Once logged in, you can delete local users with expired passwords or perform other admin tasks.
userdel -r username |
userdel -r username
You can also try to run chage to adjust the password expiration.
chage -M 180 username (extends expiration from 90 to 180 days) |
chage -M 180 username (extends expiration from 90 to 180 days)
If you continue to have login issues, you can also delete Metadata SSH keys in both the instance and project levels.
Last resort you can use force key overwrite which will regenerate a new key and overwrite broken ssh keys.
gcloud compute ssh username@servername \ --force-key-file-overwrite \ --zone us-central1-c \ --project project-id \ --internal-ip |
gcloud compute ssh username@servername \ --force-key-file-overwrite \ --zone us-central1-c \ --project project-id \ --internal-ip
Create an alias.
alias gcloud='docker run --rm -ti --volumes-from gcloud-config google/cloud-sdk:latest gcloud' |
alias gcloud='docker run --rm -ti --volumes-from gcloud-config google/cloud-sdk:latest gcloud'
Remove an alias.
unalias gcloud |
unalias gcloud
Run Terraform in a Docker container.
docker run --rm -it --name terraform -v ~/.aws:/root/.aws -v $(pwd):/workspace -w /workspace hashicorp/terraform:latest |
docker run --rm -it --name terraform -v ~/.aws:/root/.aws -v $(pwd):/workspace -w /workspace hashicorp/terraform:latest
Create an alias.
alias terraform='docker run --rm -it --name terraform -v ~/.aws:/root/.aws -v $(pwd):/workspace -w /workspace hashicorp/terraform:latest' |
alias terraform='docker run --rm -it --name terraform -v ~/.aws:/root/.aws -v $(pwd):/workspace -w /workspace hashicorp/terraform:latest'
Run the command
terraform --version
Terraform v1.0.2
on linux_amd64 |
terraform --version Terraform v1.0.2 on linux_amd64