adtac

#!/usr/bin/env -S bash -c "docker run -p 8080:8080 -it --rm \$(docker build --progress plain -f \$0 . 2>&1 | tee /dev/stderr | grep -oP 'sha256:[0-9a-f]*')"

# syntax = docker/dockerfile:1.4.0

FROM node:20

WORKDIR /root

RUN npm install sqlite3

mnutt

Example:

miguelmota

knowledge dump on container runtimes

KataContainers
- image coupled with kernel 
- light vm layer
- can run in nested virturalization environments if hardware supports and you can enable it in bios (ex. only bare metal EC2 instances, limits many cloud providers)
- slower startup time
- OCI compliant
- previously known as ClearContainers by Intel

jaymes-bearden

#!/bin/bash

# Found in user pool "General Settings / App clients" -- you can always add another if needed
APP_CLIENT_ID="abcdefg1234567"
APP_CLIENT_SECRET="a1b2c3d4e5f6g7h8i9j10"

# User details for Cognito
USERNAME=$(uuidgen) # Cognito user name -- if you don't have this aliased, use an email for the username
EMAIL="[email protected]" # Extra attributes (specified when creating the user pool)
PASSWORD="MyTestPassword!"

jaytaylor

One liner for deleting images from a v2 docker registry

Just plug in your own values for registry and repo/image name.

registry='localhost:5000'
name='my-image'
curl -v -sSL -X DELETE "http://${registry}/v2/${name}/manifests/$(
    curl -sSL -I \
        -H "Accept: application/vnd.docker.distribution.manifest.v2+json" \

stewartpark

---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: oom-killer
  namespace: kube-system
  labels:
    k8s-app: oom-killer
spec:
  selector:

elliotlarson

#!/usr/bin/env node

// Using the firebase-admin approach where database security rules do not apply.  
// Here you are authenticating with a private key. The key JSON file is available via
// the Firebase web UI: project settings > service accounts > generate new private key.

var admin = require("firebase-admin");

admin.initializeApp({
  credential: admin.credential.cert(".adminServiceAccountKey.json"),

rjz

#!/bin/sh

# ngrok's web interface is HTML, but configuration is bootstrapped as a JSON
# string. We can hack out the forwarded hostname by extracting the next
# `*.ngrok.io` string from the JSON
#
# Brittle as all get out--YMMV. If you're still reading, usage is:
#
#     $ ./ngrok_hostname.sh <proto> <addr>
#

julz

package main

import (
	"fmt"
	"os"
	"os/exec"
	"syscall"
)

func main() {

Couto

var webpack = require('webpack');
var HtmlWebpackPlugin = require('html-webpack-plugin');
var path = require('path');
var folders = {
    APP: path.resolve(__dirname, '../app'),
    BUILD: path.resolve(__dirname, '../build'),
    BOWER: path.resolve(__dirname, '../bower_components'),
    NPM: path.resolve(__dirname, '../node_modules')
};