Search…
Welcome
Home
What is Velocity?
Why Should I Use Velocity?
Terminology
Use Cases
Overview
Frontend development against an isolated environment
Develop one or more microservices
Feature collaboration
Get Started
Install CLI
Docker Compose
Create your first environment from a Docker Compose blueprint
Docker Compose Compatibility
Kubernetes & Helm
Environment Status
CLI Guides
Develop using env develop
Develop using env portal
File sync and hot reload
Connect to remote services
Environment sleep/wake up
Environment data seeding
Environment parameters
Velocity config (.velocity.yaml)
Editors
PyCharm
IntelliJ
References
CLI Reference
API Reference
Creating Blueprints (Alpha)
Overview
Velocity Annotations
Helm
Kustomize
Examples
Admin Setup
Requirements
Infrastructure Setup
FAQs
Frequently Asked Questions
Powered By GitBook
Docker Compose Compatibility
The following table presents the compatibility level of the different docker-compose features.
Docker-compose features that do not appear in the table haven't been tested by Velocity.
The table will change frequently in upcoming releases.
For more details email us at: [email protected]
Docker Compose Feature
Velocity Compatibility Level
build, build: context, build: dockerfile, build: args, build: cache_from
Only supported for local services. Offloaded services must use a public image.
command
Compatible
container_name
Not Compatible
deploy: replicas
Remote services are run with replicas=1
entrypoint
Compatible
environment
Compatible
expose
Compatible
healthcheck
Not Compatible
hostname
Not Compatible
image
Compatible
links
Not Compatible
networks
Not Compatible
networks: aliases
Not Compatible
networks: addresses
Not Compatible
ports
Compatible
ports: published
Compatible
ports: target
Compatible
secrets
Not Compatible
secrets: source
Not Compatible
secrets: target
Not Compatible
Previous
Create your first environment from a Docker Compose blueprint
Next - Get Started
Kubernetes & Helm
Last modified 2mo ago
Copy link