All packages, except for Tini have been added to termux-root. To install them, simply pkg install root-repo && pkg install docker. This will install the whole docker suite, left only Tini to be compiled manually.
| [ | |
| { | |
| "fw": "UniversalMac_11.0.1_20B28_Restore.ipsw", | |
| "file": "LLB.j274.RELEASE.im4p", | |
| "kbag": "3267519BE210D18C937A7180542EE2D66F5FBE37A0EB6BFE632B86B75C14392F2001BC3F383A7FF966F968BAB2EE484F", | |
| "key": "44a6f8571fa811690914ba053f1740400cc0931c70bd8c5a1374dd12783d84db61e89fa68a6ac4349c04b319138e7bc9" | |
| }, | |
| { | |
| "fw": "UniversalMac_11.0.1_20B28_Restore.ipsw", | |
| "file": "LLB.j293.RELEASE.im4p", |
| . ~/.antigen/init.zsh || eval "$(curl -L git.io/antigen)" | |
| antigen use oh-my-zsh | |
| antigen bundle git | |
| antigen bundle heroku | |
| antigen bundle pip | |
| antigen bundle lein | |
| antigen bundle command-not-found | |
| antigen bundle zsh-users/zsh-syntax-highlighting | |
| antigen bundle zsh-users/zsh-completions |
| version: "3" | |
| services: | |
| traefik: | |
| image: "traefik:v2.0" | |
| container_name: "traefik" | |
| command: | |
| # Globals | |
| - "--log.level=DEBUG" | |
| - "--api=true" |
| #!/usr/bin/env bash | |
| # Print a message | |
| # | |
| # Params: | |
| # $1: colour (red | green | yellow) | |
| # $*: status to print | |
| # | |
| # Example usage: | |
| # print_msg green "Successfully built $something" |
| <!-- Instructions: | |
| - Download and unzip Mojave dynamic background here: https://files.rb.gd/mojave_dynamic.zip | |
| - Rename the extracted folder as "mojave-background" (Excuse the trouble but I renamed it on my machine and already use that path in the XML file) | |
| - Save this xml file next to the Mojave background files | |
| - Fix the path to the background images below (better using absolute path) | |
| - Lastly, either: | |
| + GNOME: Use gnome-tweaks tool to select this XML as wallpaper (as default wallpaper settings won't let you choose wallpaper from custom path) | |
| + MATE: Go to background setting (in Appearance) > Choose +Add... > make sure **All files** filter is selected at the bottom right > Then choose mojave.xml | |
| --> | |
| <background> |
The official guide for setting up Kubernetes using kubeadm works well for clusters of one architecture. But, the main problem that crops up is the kube-proxy image defaults to the architecture of the master node (where kubeadm was run in the first place).
This causes issues when arm nodes join the cluster, as they will try to execute the amd64 version of kube-proxy, and will fail.
It turns out that the pod running kube-proxy is configured using a DaemonSet. With a small edit to the configuration, it's possible to create multiple DaemonSets—one for each architecture.
Follow the instructions at https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/ for setting up the master node. I've been using Weave Net as the network plugin; it see
I owe my very rapid learning journey in the world of ConfigFs to several key sources which aren't necessarily relevant to this result, but I feel deserve a mention anyway.
- This really demystified configfs for me, and stopped me being afraid of it: http://events.linuxfoundation.org/sites/events/files/slides/USB%20Gadget%20Configfs%20API_0.pdf
- I borrowed heavily from this Mindstorms EV3 script: https://github.com/ev3dev/ev3-systemd/blob/ev3dev-jessie/scripts/ev3-usb.sh
- Desperately trawled this thread for answers: https://answers.microsoft.com/en-us/windows/forum/windows_10-networking-winpc/windows-10-vs-remote-ndis-ethernet-usbgadget-not/cb30520a-753c-4219-b908-ad3d45590447?auth=1
- This guide is handy: http://irq5.io/2016/12/22/raspberry-pi-zero-as-multiple-usb-gadgets/