, , _______________________________
,-----------|'------'| | |
/. '-' |-' |_____________________________|
|/| | |
| .________.'----' _______________________________
| || | || | |
\__|' \__|' |_____________________________|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
prep: | |
helm repo add nvidia https://helm.ngc.nvidia.com/nvidia \ | |
&& helm repo update | |
install: | |
helm install --wait nvidiagpu \ | |
-n gpu-operator --create-namespace \ | |
--set toolkit.env[0].name=CONTAINERD_CONFIG \ | |
--set toolkit.env[0].value=/var/lib/rancher/k3s/agent/etc/containerd/config.toml \ | |
--set toolkit.env[1].name=CONTAINERD_SOCKET \ |
While k3s
and RKE2
ship with their own statically-compiled containerd binary, sometimes you need to be able to utilize a more standard container socket. Especially if your container-scanner expects a more traditional installation path (i.e. Twistlock/PrismaCloud). This quick guide will show you how to get up and running with an external CRI.
There are better ways to do this, but the most common way of installing containerd is via the docker-ce
yum repository.
sudo yum-config-manager \
--add-repo \
https://download.docker.com/linux/centos/docker-ce.repo
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
204 password | |
193 123456 | |
144 admin | |
125 support | |
116 123 | |
114 1234 | |
105 default | |
99 12345 | |
97 1 | |
84 ubnt |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
## https://forum.proxmox.com/threads/console-failed-to-connect-to-server-host-key-verification-failed.78957/ | |
# Usage: ./proxmox_webvnc_fix.sh <shorthostname> | |
# Notes: may need to run twice for the fix to take. | |
set -e | |
DOMAIN="lark.lol" | |
if [ $# -eq 0 ]; then | |
echo "No hostname provided. Exiting..." |
Nothing about this is turnkey. It's a mess of protocols, firmware and apps, but if you're the right kind of nuts, keep reading.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## | |
## shoutout to https://github.com/webosbrew | |
## I lifted these instructions from the #OpenLGTV discord (under pinned msgs). The instructions are for Windows but just replace Putty with a terminal and you're good to go. | |
1. Enable Developer Mode: https://webostv.developer.lge.com/develop/getting-started/developer-mode-app | |
2. Download Software: | |
a. WebOS-Dev-Manager - https://github.com/webosbrew/dev-manager-desktop/releases | |
b. PuTTY - https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html | |
c. Homebrew Channel 0.5.1 ipk - https://github.com/webosbrew/webos-homebrew-channel/releases | |
3. In WebOS-Dev-Manager perform these steps: |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
--- | |
- hosts: all | |
tasks: | |
# ansible all -i closet.lark.lol -u root coral-playbook.yaml | |
# deb https://packages.cloud.google.com/apt coral-edgetpu-stable main | |
# https://packages.cloud.google.com/apt/doc/apt-key.gpg | |
- name: Add an Apt signing key, uses whichever key is at the URL | |
ansible.builtin.apt_key: | |
url: https://packages.cloud.google.com/apt/doc/apt-key.gpg |
### Assumptions:
# - Registry: You have a private registry (ex: harbor.air-gap.dev) pre-seeded with required images
# - File Dependencies:
# - SELinuxRPM: k3s requires an selinux rpm. You can grab it ahead of time from here: https://github.com/k3s-io/k3s-selinux/releases
# - k3s binary: (example) https://github.com/k3s-io/k3s/releases/download/v1.24.4%2Bk3s1/k3s
NewerOlder