nkhine

import { App, RemovalPolicy } from '@aws-cdk/core';
import { MultistackStack, MultistackProps } from './stacks/multistack';
import { PipelineStack, PipelineStackProps } from './stacks/pipeline';

const prodEnv = {
  account: '***',
  region: 'eu-west-1',
};

const app = new App();

nkhine

Create a dedicated ZFS docker pool with deduplication disabled in case of dedup enabled on your system:

zfs create -o mountpoint=/var/lib/docker -o dedup=off rpool/docker

Sometimes, you don't want ZFS for docker storage. ZFS can be sadly quite painful with Docker in Docker and similar scenarios. It might be best to avoid the problem by creating a volume in your ZFS pool, formatting that volume to ext4, and having docker use "overlay2" on top of that, instead of "zfs".

zfs create -s -V 30G rpool/docker

mkfs.ext4 /dev/zvol/rpool/docker

nkhine

-- Logs begin at Wed 2021-05-12 15:18:03 UTC, end at Wed 2021-05-12 15:21:24 UTC. --
May 12 15:18:03 kind-control-plane systemd[1]: Starting containerd container runtime...
May 12 15:18:03 kind-control-plane systemd[1]: Started containerd container runtime.
May 12 15:18:03 kind-control-plane containerd[188]: time="2021-05-12T15:18:03.817611995Z" level=info msg="starting containerd" revision=ce4439a8151f77dc50adb655ab4852ee9c366589 version=v1.4.0-106-gce4439a8
May 12 15:18:03 kind-control-plane containerd[188]: time="2021-05-12T15:18:03.844535348Z" level=info msg="loading plugin \"io.containerd.content.v1.content\"..." type=io.containerd.content.v1
May 12 15:18:03 kind-control-plane containerd[188]: time="2021-05-12T15:18:03.844626453Z" level=info msg="loading plugin \"io.containerd.snapshotter.v1.aufs\"..." type=io.containerd.snapshotter.v1
May 12 15:18:03 kind-control-plane containerd[188]: time="2021-05-12T15:18:03.844672989Z" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.aufs" error

nkhine

<#
- BIOS of host machine also needs to be configured to allow hardware virtualization
- This gist WSLv2, but can use WSLv1 instead. I needed v1 as I run Windows 10 in a VM in Virtualbox.
- WSLv2 has been giving me problems in Virtualbox 6.1, but WSLv1 works properly.
- vbox has issues with the GUI settings when it comes to nested virtualization on certain systems,
  so run the following if needing to give a VM this enabled setting:

  VBoxManage modifyvm <vm-name> --nested-hw-virt on
#>

nkhine

# Backup
docker exec CONTAINER /usr/bin/mysqldump -u root --password=root DATABASE > backup.sql

# Restore
cat backup.sql | docker exec -i CONTAINER /usr/bin/mysql -u root --password=root DATABASE

nkhine

---
AWSTemplateFormatVersion: '2010-09-09'
Description: 'Crucible: highly available Fisheye/Crucible template.'
Metadata:
  'AWS::CloudFormation::Interface':
    ParameterGroups:
    - Label:
        default: 'Parent Stacks'
      Parameters:
      - ParentVPCStack

nkhine

#! /bin/sh
### BEGIN INIT INFO
# Provides: vpnclient
# Required-Start: $all
# Required-Stop: $network $local_fs $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start VPN Client at boot time
# chkconfig: 345 44 56
# description: Start VPN Client at boot time.

nkhine

```
Thread Dump
DestroyJavaVM

"DestroyJavaVM" Id=22 Group=main RUNNABLE

FilePath.localPool [#7]

"FilePath.localPool [#7]" Id=94 Group=main RUNNABLE
	at sun.management.ThreadImpl.dumpThreads0(Native Method)

nkhine

Administrator CMD
C:\> hcsdiag list
C:\> hcsdiag kill wsl
C:\> wsl -l
C:\> wsl -d alpine
LOE-WSL:/mnt/c#

nkhine

layout	title	date	categories
post	SELinux and docker notes	2018-02-13 13:13:59 +0200	docker selinux

SELinux and docker notes

What it takes to run our containers with SELinux enabled.