Deoren Moor deoren

Useful LXD commands

Summarized from https://stgraber.org/2016/03/19/lxd-2-0-your-first-lxd-container-312/.

Interestingly, the LXD command line client is named.... lxc!

List available containers

lxc image list ubuntu:        # ubuntu: is officially supported image source
lxc image list images:        # images: is an unsupported source
lxc image alias list images:  # lists user-friendly names

This is intended for copying/pasting as the first comment to all Gist entries I create. It's unfortunate that GitHub doesn't support notifying creators and participants in the feedback process for Gists, but this is at least something I can do to let potential viewers know that I'm not intentionally ignoring them.

As of the time this Gist entry was created, GitHub does not support notifications for comments for mentions to Gist entries (see isaacs/github#21 for details). Please contact me via Twitter or file an issue in the deoren/leave-feedback repo (created for that very purpose) if you wish to receive a response for your feedback. Thank you in advance!

Story: Writing Scripts with Go

This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.

Why Go is good for scripting?

While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.

How to create a LXD Container with your ssh key in it (and with ssh server in the container)

Create a brand new ed25519 key pair

ssh-keygen -o -a 100 -t ed25519

Get the pub key and put the result in your lxd default profile

cat ~/.ssh/ed25519.pub
lxc profile edit default

Microsoft Visual C++ 2005 Redistributable Package (x64)

Microsoft Visual C++ 2005 Redistributable Package (x86)

Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)

Microsoft Visual C++ 2005 SP1 Redistributable Package (x64)

Microsoft Visual C++ 2008 Redistributable Package (x64)

In case you want to run ansible (or ansible-playbook) command against a set of hosts that makes sense only for one run, you can don't bother to create one-time inventory file, but simply define a comma-separated list of hosts as argument of --invertory option (or its short form that's simply -i) as follows:

ansible --inventory=myhost1,myhost2,myhost3 all -m setup -a 'filter=*name*'

(note that all in this command line stands for the target hostname)

If you have only one host to run your playbook against, your inventory string must ends with ,

	---
	- hosts: localhost
	gather_facts: no
	vars:
	docker_volume: db_data
	docker_network: ansible_net
	db_name: db
	wp_name: wordpress
	wp_host_port: 8000
	wp_container_port: 80

	# create the network if network does not exist
	docker network list \| grep -q "wordpress_net" \|\| \
	docker network create "wordpress_net"

	# create volumes
	docker volume create -d local --name "db_data"

	# start mysql database
	docker run -d \
	-v db_data:/var/lib/mysql:rw \

	#!/bin/sh

	# Credits: http://stackoverflow.com/a/750191

	git filter-branch -f --env-filter "
	GIT_AUTHOR_NAME='Newname'
	GIT_AUTHOR_EMAIL='new@email'
	GIT_COMMITTER_NAME='Newname'
	GIT_COMMITTER_EMAIL='new@email'
	" HEAD

	bash -c 'while [[ "$(curl -s -o /dev/null -w ''%{http_code}'' localhost:9000)" != "200" ]]; do sleep 5; done'

	# also check https://gist.github.com/rgl/c2ba64b7e2a5a04d1eb65983995dce76