Five simple StackEngine trial tips, when StackEngine is installed on a host already used for Docker.
Install –
Easily copy and paste install
In order to really get the feel for the power and scale of StackEngine, you must first install the downloaded software onto at least one of your servers. Our most common install method is to simply download and run the binary in /usr/local/stackengine. We make this easy with a copy and paste install, that sets everything up for you on the host. Then, you simply login to the locally running instance of StackEngine on the IP address and port 8000 of that server (conveniently shown to you as part of the output of the StackEngine install script). If you need more guidance on installing StackEngine, check out our documentation, including sections on other install methods and trial licenses: docs.stackengine.wpengine.com
How many images are in your environment? – From the main dashboard, find the number of total images in the upper right.
Docker image count
Does the number surprise you? Is it large? Click on it. From here, you will navigate to the Images screen, where you will see all of the images that have been downloaded across your hosts. Image sprawl can consume more disk than you might want. It’s actually very easy to remove any of the local images that might be cluttering up your server. Simply select the remove button associated with any image or use the bulk remove options, that are shown at the bottom of the listing.
Start, Stop or Pause a Container – Now, navigate to the Container screen via the left nav. Do you see any containers? What is their current status? Are any stopped or paused, that should be running? Is that surprising?
Stopped containers are easily found
Try changing the running status of a container. Simply select one and click the button to start, stop or pause the container. That was pretty easy, right? Is it helpful to see containers, that may be in a state that was not planned, like being stopped, when you expect that they would be running?
Hint – In larger, multi-host environments, you can easily use the filtering to find all stopped containers or out of date docker binaries! You can even further filter on another dimension, such as name, for example “redis”. Filtering is fast and easy, and will scale across hundreds of hosts, and thousands of images and containers.
Launch an Image as a Container. Try running an image as a container. To do this, just pick any image that you want that exist on any of your hosts, and select the Run button associated with it. From here, you will be shown all the parameters that you might want to use, including advanced options. When ready, just select “Go”
Note, if no images exist already on your hosts, you will need to setup a component to pull an image from an image registry.
View the Container Log. If you were trying to view a containers docker log with the Docker CLI, you would need to know the container id. With StackEngine, simply use the search function (left nav Search). From there, you can search for a particular container by name. Then just select the container you want to drill into the details and then select “View Logs”. This is a nice point and click convenience feature.
Easily view the log of any Docker container
These StackEngine trial tips are just the beginning of the functionality available in the product. If you require any assistance at all with your StackEngine trial, we are here to help. Simply email: support [at] stackengine.wpengine.com.
The post StackEngine Trial Tips appeared first on StackEngine.