The short answer
No. To deploy one app on Antideploy you do not need Docker, Kubernetes or YAML. Antideploy reads your project, works out how to build and start it, and does the packaging itself. You can add a Dockerfile if you want exact control, and then Antideploy uses it.
What each one is
-
Docker packs an app and everything it needs into one sealed unit called a container, so it runs the same everywhere.
-
A Dockerfile is the recipe for that container. It lists the steps to build it.
-
Kubernetes runs and manages many containers across many machines. It is built for teams that run many services at large scale. One app does not need it.
-
YAML is a file format for settings. Kubernetes, GitHub Actions and many hosts use YAML files to describe what to run.
What happens on Antideploy instead
Antideploy reads your files and builds the container for you, using standard buildpacks. It works out the language and version, the install and build commands, the start command and the port. It tells you what it found and which file each answer came from.
You write no recipe and no YAML. If your project has a Procfile with a web: line, that line is used as the start command. That is one line, and it is optional.
When a Dockerfile is worth writing
- Your app needs a system program that is not a package, such as
ffmpegor an image library - Your project is PHP, which runs only through a Dockerfile
- You need an exact language version or build steps that the automatic build does not guess
- You already have a Dockerfile that works and want it used as it is
If there is a Dockerfile at the root of your project, Antideploy builds with it. Its own start command is used, and the port it declares with EXPOSE is the one Antideploy sends traffic to. Read how to deploy with your own Dockerfile for the details and the limits.