Brett Taylor ssplatt

Uses https://github.com/docker/docker-ce/blob/master/components/packaging/deb/ubuntu-xenial/Dockerfile.aarch64

on your odroid using the ubuntu-xenial image from hardkernel. for example, http://east.us.odroid.in/ubuntu_16.04lts/ubuntu64-16.04.3-minimal-odroid-c2-20171005.img.xz

apt install git docker.io
git clone https://github.com/docker/docker-ce
cd docker-ce
git checkout 17.12

Superalgos Docker Basics

Introduction

This walkthrough is broken up into to parts: a quick-start guide to running Superalgos with Docker and a deeper, more theoretical dive into containers with the hopes of explaining some of the design decisions.

Superalgos, at its core, is a web application which also means it can be deployed inside a container like many other web applications. One of the leading platforms for operating containers is Docker. Docker can run on many different operatng systems and compute platforms. The containers provide an easy, fast, repeatable, and secure way to deploy and distribute applications. While it doesn't take much experience to run containers or Docker, there are some basics that any user should learn in order to use the technology effectively.

Before getting started, be aware that Docker is not the originally intended method of running the [Superalgos](https://github.com/Superalgos/S

	version: "3"
	services:
	znc:
	image: znc
	volumes:
	- /opt/docker-persist/znc:/znc-data
	ports:
	- 5678:5678
	restart: always

	nodejs::repo_url_suffix: 6.x
	nodejs::npm:
	my-custom-app:
	ensure: "present"
	user: www
	target: "/var/www/apps/my-custom-app"
	use_package_json: true

	class myapp (){
	file { '/opt/serverapp':
	ensure => 'directory',
	owner => 'myuser',
	group => 'myuser'
	}

	nodejs::npm { 'express from the npm registry':
	ensure => 'present',
	package => 'express',

	context 'create npm resources' do
	let(:facts) do
	facts
	end
	let('nodejs::npm') do
	{
	'myapp' => {
	'ensure' => "present",
	'target' => "/var/www/apps/myapp",
	'use_package_json' => true

	apiVersion: extensions/v1beta1
	kind: DaemonSet
	metadata:
	creationTimestamp: null
	generation: 1
	labels:
	k8s-app: kube-proxy-amd64
	name: kube-proxy-amd64
	selfLink: /apis/extensions/v1beta1/namespaces/kube-system/daemonsets/kube-proxy-amd64
	namespace: kube-system

	sysbench --test=cpu --cpu-max-prime=20000 --num-threads=$(cat /proc/cpuinfo \| grep processor \| wc -l) run
	sysbench 0.4.12: multi-threaded system evaluation benchmark

	Running the test with following options:
	Number of threads: 4

	Doing CPU performance benchmark

	Threads started!
	Done.

	---
	kind: ClusterRole
	apiVersion: rbac.authorization.k8s.io/v1beta1
	metadata:
	name: flannel
	rules:
	- apiGroups:
	- ""
	resources:
	- pods