Services
Docker services
Docker Services run a container image you choose: public or private registry, ports, variables, and when to prefer Docker over App.
A Docker Service runs a container image you specify. Use it when you already publish an image (CI builds elsewhere, third-party software, or a stack that does not fit a Git-backed App Service).
Compare with App services (build from Git inside dFlow) and Database services (managed engines; see Databases overview under Databases in the sidebar).
What you configure
- Image: public image URL, or private image with a linked registry account. See Docker registry integration under Integrations in the sidebar.
- Ports: expose the ports your process listens on, as prompted in the UI.
- Variables: same Service settings model as App Services: static values,
secret(), and reference variables to database Services. - Volumes: attach persistent disks when the UI offers Volumes for Docker Services. See Volumes and persistent storage under Deployments and Operations in the sidebar.
When to choose Docker vs App
| Choose App | Choose Docker |
|---|---|
| You develop in Git and want dFlow to build the repo. | You only have (or only want) a pre-built image. |
| You use supported buildpacks or Dockerfile flows in the product. | You run vendor images, legacy artifacts, or custom entrypoints. |
Connecting to databases
Use Reference variables on the Docker Service Variables tab, same as App Services. See Service settings and Databases overview under Databases in the sidebar.
If deploy fails
- Deployment issues under Troubleshooting in the sidebar
- Logs under Deployments and Operations in the sidebar and Logs and debugging under Troubleshooting in the sidebar
- Integration issues under Troubleshooting in the sidebar for registry authentication