Skip to content

Containers are dropped silently and randomly due to resources on deploy() #3

@gapan

Description

@gapan

Here is an example scenario: on a host with 16GB RAM, I'm trying to run 20 containers with 1GB RAM allocated each.

When running fogify.deploy() I get an OK message, that everything is deployed. But that is not true. In fact, at least 4 of my containers are never started and the choice seems to be random. It appears that fogify checks the sum of resources needed against the host system and does not start any containers that exceed the host system resources (but not the actual available host resources, i.e. it checks against the total of 16GB, but not against the 8GB that may possible be actually available at that point, I guess that's another issue?).

I'm not sure if not starting the containers at all is the right course of action here. After all, I am able to start as many (or more) such containers in my system without fogify, or even by using fogify and setting lower RAM limits. But my main issue is that it all happens silently and the user is left to believe that everything went well and all containers are up.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions