Alphaus | Documentation
WebsiteRepoTech blog (JP)Tech blog (EN)
ALM v2.0
ALM v2.0
  • Mobingi Documentation (v2.0)
  • Getting started
  • Guides and tutorials
    • Stack lifecycle
      • Deploy stack
      • Manage stack
    • Docker
      • Custom Docker containers
    • Others
      • Blue-green deployment
      • How to use RDS
      • Environment variables
      • Custom installation script
      • SSH into your container
    • FAQ
  • API Reference
    • Overview
    • Stacks
      • List stacks
      • Create stack
      • Describe stack
      • Update stack
      • Delete stack
      • Deploy code
      • Put lifecycle hook
      • Get lifecycle hook
      • Restart instance
      • Describe ServiceConfig
      • Update ServerConfig
    • Vendor credentials
      • List credentials
      • Save credentials
      • Delete credentials
Powered by GitBook
On this page
  • Deploy custom Docker containers
  • Configuration file

Was this helpful?

  1. Guides and tutorials
  2. Docker

Custom Docker containers

PreviousDockerNextOthers

Last updated 6 years ago

Was this helpful?

Deploy custom Docker containers

It is possible to deploy your own docker container on mobingi ALM. Simply type in the name of your docker image on docker hub and you are ready to go.

Docker images that are not modified to have a configuration file and container_status files will not be able to take advantage of , and code deploys will write into the /var/www folder.

Mobingi ALM also automatically maps port 80 and 443 exposed by the container to the port 80 and 443 respectively on the machine. Other ports are ignored.

Configuration file

If a custom docker container does not have a configuration file, mobingi ALM will immediately switch new connections to the new container the moment it starts. If your docker container needs to perform certain tasks before it is able to start, it needs to signal that it is ready to accept connections.

Without a configuration file also, mobingi ALM will only deploy code into the /var/www folder.

In order to enable and specify a specific folder for the code deploys to place code in, the container must have the following things:

  • A config file in the root directory

  • The startup command must write running into the /var/log/container_status file when it is ready to accept connections.

This is an example config file:

{
   "codeDirectory": "/srv/code"
}
Blue-Green Deployment
Blue-Green Deployment