Introductory FAQs
General questions about the deployment process on StackOS.
A Docker Image is like a game cartridge for servers. When you "insert the cartridge" into a game system, you know the system will run the exact software you have prepared.
The "Docker Style" style of running systems is rapidly being adopted because a tested system does not change across deploys.
Previous methods of setting up a system from scratch often introduced "setup variance" which caused the same software to run differently, leading to higher debugging costs.
Yes, StackOS is happy to help your project onboard to Docker and StackOS. Please reach out to us on telegram.
Apps in the StackOS AppStore are "quick launch" docker containers that allow users to run software with less configuration.
These address common needs.
Probably. StackOS can run any docker image, so if you see it on hub.docker.com you can probably run it on StackOS
Yes, simply place your image on hub.docker.com and it will be available to run.
Typical startups avoid Kubernetes because 1) it is a layer of complexity they may not fully understand and 2) is not the core deliverable to the end-user.
Furthermore, for smaller startups, once their sys-admins learn Kubernetes, they often depart for higher paying jobs in other companies.
As a result, Docker infrastructure can often be left "brittle" and without failover, and in the worst cases without an admin until a suitable skilled replacement can be found.
With StackOS, running on a reliable Kubernetes platform is no harder than running basic Docker images.
Join our Discord and ask your questions in the #dev-support channel.
Last modified 10mo ago