You are here

Error message

  • Deprecated function: Methods with the same name as their class will not be constructors in a future version of PHP; views_display has a deprecated constructor in require_once() (line 3279 of /home/blackh31/public_html/BLACKHILL/includes/bootstrap.inc).
  • Deprecated function: Methods with the same name as their class will not be constructors in a future version of PHP; views_many_to_one_helper has a deprecated constructor in require_once() (line 127 of /home/blackh31/public_html/BLACKHILL/sites/all/modules/ctools/ctools.module).
  • Deprecated function: The each() function is deprecated. This message will be suppressed on further calls in menu_set_active_trail() (line 2396 of /home/blackh31/public_html/BLACKHILL/includes/menu.inc).

Blog

Amazon Web Services: Tunneling SVN over SSH

After installing Subversion in an Amazon EC2 instance, set the Security group to allow SSH from your IP and SVN from the EC2 instance's IP.
Connect to the Amazon EC2 instance using the key provided by Amazon and forward the Local SVN port to the Remote SVN port.
ssh -i ~/.ssh/AWS-ubuntu-key.pem ubuntu@xxx.xxx.xxx.xxx -L 3690:xxx.xxx.xxx.xxx:3690
You should now be able to connect to your remote SVN server via SSH tunnel using:
svn co svn://localhost/repository

So, you need access into a Docker container...

One of the ideas behind Docker containers is that you create a sandbox environment segregated from the host environment in such a way that the configuration of the container can be guaranteed.  However, when planning a Docker deployment, it can be useful to log into the container to troubleshoot unforeseen issues.  As long as the lessons learned get conveyed into the Dockerfile and the image is rebuilt, then the original containerization intent can be achieved.
# show full id
sudo docker ps --notrunc
# use lxc-attach
sudo lxc-attach -n <full-id>
 

Installation of Webmin Server Administration Tool

If you like to install and update Webmin via APT, edit the /etc/apt/sources.list file on your system and add the lines :

deb http://download.webmin.com/download/repository sarge contrib
deb http://webmin.mirror.somersettechsolutions.co.uk/repository sarge contrib

You should also fetch and install my GPG key with which the repository is signed, with the commands :

cd /root
wget http://www.webmin.com/jcameron-key.asc
apt-key add jcameron-key.asc

You will now be able to install with the commands :

Thin-Client Based Developer Environment in Docker Containers

Okay, so we have a number of examples where bits and pieces of a thin client development environment have been mounted within Docker Containers.

LAMP using Docker Part I Installation of ICEcoder within Docker Adding a Browser-based Image Editor to ICEcoder

To tie it all together, we've added a web-based SVN client and wrapped it all with a shell script to build the environment for you.

Adding a Browser-based Image Editor to ICEcoder

These instructions require the ICEcoder Docker install (http://lastmilesynergy.com/?q=node/49) to have already been completed.

Download SVG-edit from https://code.google.com/p/svg-edit/ and place it in a folder.

In that same folder, 

$ touch Dockerfile

and fill it with the following instructions:

Creating a Local Docker Registry

To create a Docker Registry, execute the following CLI to download the stackbrew/registry image and run it.

$ sudo docker run -d -p 127.0.0.1:5000:5000 stackbrew/registry

Now, determine what the image id is for the Docker image you want to store within the registry:

Installation of ICEcoder within Docker

ICEcoder (http://icecoder.net) is a code editor which runs within the developer's browser.  The below Dockerfile builds on the apache-php image we've already created (http://lastmilesynergy.com/?q=node/46).

From within a new directory, create an empty Dockerfile and download the ICEcoder zip file (http://icecoder.net/download-zip).

$ touch Dockerfile
$ wget http://icecoder.net/download-zip

LAMP using Docker Part II

Putting the M in LAMP

In Part I we built a Dockerfile to generate the LAP part of a LAMP server.  Now, all we need to do is add instructions to a Dockerfile in order to install and start MySQL.

LAMP using Docker Part I

Putting the LAP in LAMP

Assuming you have Docker installed and have a docker user within a docker group, you're ready to set up a Linux-Apache-MySQL-PHP (LAMP) Server.

As root, launch a container from the ubuntu image (not base):

$ sudo docker run -i -t ubuntu \bin\bash

In the launched container, install PHP and Apache2.

# apt-get install php5
# apt-get install apache2

Assuming everything goes well, exit the container and view the list of containers with "sudo docker ps -a".

Docker Security

The docker daemon always runs as root, and since docker version 0.5.2, docker binds to a Unix socket instead of a TCP port. By default that Unix socket is owned by the user root, and so, by default, you can access it with sudo.

Pages

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer