Difference between revisions of "Shipyard"

From SME Server
Jump to navigationJump to search
 
Line 1: Line 1:
{{WIP box}}
+
{{Warning box|content is obsolete. Shipyard is not maintained.}}{{WIP box}}
  
 
==Shipyard web GUI==
 
==Shipyard web GUI==

Latest revision as of 03:24, 27 April 2018

Warning.png Warning:
content is obsolete. Shipyard is not maintained.


Warning.png Work in Progress:
This page is a Work in Progress. The contents off this page may be in flux, please have a look at this page history the to see list of changes.


Shipyard web GUI

Shipyard is a separate GUI project hosted on Github. It will allow you to manage Docker instances and images from your browser. It is not required to use and run Docker containers, for all Docker commands can be issued from the command line.

For Shipyard to be able to connect to the Docker deamon, the file /etc/sysconfig/docker has to be adjusted to enable socket support and TCP.

Templated /etc/sysconfig/docker based on below db settings

/etc/sysconfig/docker:

other_args="-H tcp://127.0.0.1:4243 -H unix:///var/run/docker.sock"

127.0.0.1 (localhost) or 0.0.0.0 (public) based on db key shipyard Access

The restart the Docker deamon:

service docker restart

For Shipyard to be able to manage (multiple) hosts, each and every hosts will need to have shipyard-agent installed.


Installation

Shipyard can be installed as a Docker application itself. We will use this way of installing Shipyard.

Issue the follwoing command as root:

docker run -i -t -v /var/run/docker.sock:/docker.sock shipyard/deploy setup

This will make Docker pull the various layers and images and combine it into fully functional webserver with the Shipyard application installed.

Loose notes:

config set shipyard service TCCPort 4243 access public status enabled
signal-event remoteaccess-update
shipyard=service
TCPPort=4243
access=public
status=enabled


Shipyard agent

About


Installation

TBA

Loose notes

shipyard-agent=service
TCPPort=8000;4500
access=public
status=enabled