Renan-Di

#! /bin/bash
mkdir ~/start-scripts
cat <<EOF >> ~/start-scripts/change-mtu.sh
#! /bin/bash
ip link set dev eth0 mtu 1350
EOF
chmod +x ~/start-scripts/change-mtu.sh
echo "sudo ~/start-scripts/change-mtu.sh" >> ~/.bashrc
sudo -i
echo "$USER    ALL=NOPASSWD: $HOME/start-scripts/change-mtu.sh" | EDITOR='tee -a' sudo -n -e /etc/sudoers.d/mtu

angelbarrera92

#!/bin/bash

# Create the cluster
kind create cluster --name lb
# Get the configuration
kind get kubeconfig --name lb > /tmp/lb-kubeconfig
# Deploy metallb
KUBECONFIG=/tmp/lb-kubeconfig kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.9.5/manifests/namespace.yaml
KUBECONFIG=/tmp/lb-kubeconfig kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.9.5/manifests/metallb.yaml
KUBECONFIG=/tmp/lb-kubeconfig kubectl create secret generic -n metallb-system memberlist --from-literal=secretkey="$(openssl rand -base64 128)"

lucj

for node in node1 node2 node3;do
  multipass launch -n $node
done

# Init cluster on node1
multipass exec node1 -- bash -c "curl -sfL https://get.k3s.io | sh -"

# Get node1's IP
IP=$(multipass info node1 | grep IPv4 | awk '{print $2}')

zoilomora

How to disable systemd-resolved in Ubuntu

Stages

• Disable and stop the systemd-resolved service:

    sudo systemctl disable systemd-resolved.service
    sudo systemctl stop systemd-resolved
  

• Then put the following line in the [main] section of your /etc/NetworkManager/NetworkManager.conf:

rwenz3l

Installing NFS inside LXC Container on Proxmox 5.1

Host Setup:

Create LXC Container as usual, but do not start it yet.

# Install NFS-Kernel on Host
apt install nfs-kernel-server

jonathan-kosgei

I have been an aggressive Kubernetes evangelist over the last few years. It has been the hammer with which I have approached almost all my deployments, and the one tool I have mentioned (shoved down clients throats) in almost all my foremost communications with clients, and it was my go to choice when I was mocking my first startup (saharacluster.com).

A few weeks ago Docker 1.13 was released and I was tasked with replicating a client's Kubernetes deployment on Swarm, more specifically testing running compose on Swarm.

And it was a dream!

All our apps were already dockerised and all I had to do was make a few modificatons to an existing compose file that I had used for testing before prior said deployment on Kubernetes.

And, with the ease with which I was able to expose our endpoints, manage volumes, handle networking, deploy and tear down the setup. I in all honesty see no reason to not use Swarm. No mission-critical feature, or incredibly convenient really nice to have feature in Kubernetes that I'm go

amaksoft

#!/usr/bin/groovy

/*
 * Copyright (c) 2016, Andrey Makeev <[email protected]>
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright

deviantony

#!/bin/bash


## THIS IS THE OLD WAY
## Nowadays, simply follow the Compose installation instructions in the official documentation: 
## https://docs.docker.com/compose/install/


# get latest docker compose released tag
COMPOSE_VERSION=$(curl -s https://api.github.com/repos/docker/compose/releases/latest | grep 'tag_name' | cut -d\" -f4)

briandk

Contributing to Transcriptase

We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:

• Reporting a bug
• Discussing the current state of the code
• Submitting a fix
• Proposing new features
• Becoming a maintainer

We Develop with Github

shamil

How to mount a qcow2 disk image

This is a quick guide to mounting a qcow2 disk images on your host server. This is useful to reset passwords, edit files, or recover something without the virtual machine running.

Step 1 - Enable NBD on the Host

modprobe nbd max_part=8