OverviewCreate a proxyDeploymentExample dockerfilesPricing

Getting started with containers

Creating containers

  1. Creata a container by navigating to your project:
    1. Click add a service.
    2. Click 'container' service.
    3. Select your usage environment, you can select from 256 MB ram to 8 GB of ram, and from 1 CPU to 4 CPU's.
    4. Select the right amount of containers, X-Scaling is automaticly enabled for container types: Production, and Enterprise. This program will ensure that the right amount of containers are deployed at the specific time. So we try to make sure you are not charged the maximum amount. However, setting the maximum to low, or having a load that will continuously is very high. You might be charged the full amount.
  2. Attach your domain name to your container.
    1. Navigate to your container, select domains, add your domain.
    2. You will be prompted to create CNAME records.
    3. Verify your configuration by clicking 'verify configuration'.
  3. Create a Dockerfile, you will be able to see example dockerfiles here.
    • You can verify if your setup is correct by running docker build -t test .
  4. Deploy your container by running: npx @aurtic/cli@latest container deploy

How containers work

A container is a single process that is run on multiple servers. Each container has its own filesytem, networking, etc. A container acts, in some ways very much like a traditional Virtual Machine.

Auto scaling

Containers will automaticly scale up and down based on your current demand. We track your usage and based on some algorithmic rules, and an AI, we determine how many containers we deploy.

Storing files

You can store files directly into your docker container. Note that all files writton onto the container are not preserved. Whenver that specifc process is moved, it will lose its storage and reset to its original state. We recommend using a database, or Archives to store files as files are preserved.

Networking

The container can access the outside world through the IP of the overlaying server. Containers cannot open ports by themselfs. We have created the proxy system. A proxy is a way the outside world can communicate with the deployed containers through HTTP. More info on how to create proxies can be found here