You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why do you need this?
We are seeking guidance on deploying OpenFaaS in a Docker Compose environment that is not managed by Swarm, specifically for custom projects tailored to the needs of smaller clients.
Expected Behaviour
A feasible method to deploy OpenFaaS components using Docker Compose in Standalone Mode, allowing us to publish functions as we would in a Swarm environment.
Current Behaviour
Currently, we are unable to find documentation or examples that illustrate deploying OpenFaaS in a non-Swarm Docker Compose setup.
Utilizing faasd as a potential solution for deploying OpenFaaS functions via Docker Compose.
Seeking alternative methods or configurations that are not explicitly documented.
Which Solution Do You Recommend?
We are open to suggestions from the community and maintainers. If faasd is a viable option, we are willing to consider it.
Context
We are a company that has successfully integrated OpenFaaS into our SaaS project and are now looking to extend this to smaller, custom projects. We believe that using Docker Compose in Standalone Mode will help us conserve resources while still providing a robust solution for our clients.
Your Environment
Docker version docker version (e.g. Docker 17.0.05 ):
26.1.1
Currently, we are unable to find documentation or examples that illustrate deploying OpenFaaS in a non-Swarm Docker
Sorry, OpenFaaS does not support Docker Swarm at all or docker-compose. It's a platform for deploying functions to Kubernetes, and perhaps what you really need is OpenFaaS Standard, plus a Helm chart for your functions.
We believe that using Docker Compose in Standalone Mode will help us conserve resources while still providing a robust solution for our clients.
If you'd like to deploy OpenFaaS in an edge configuration, you have two options: faasd for a single node, or OpenFaaS Standard for commercial features and the benefits of packaging you asked for. With faasd, you will need to perform an initial deployment of your functions after the installation.
We are a company that has successfully integrated OpenFaaS into our SaaS project
The OpenFaaS CE EULA doesn't allow for commercial use, a license will be required for your SaaS, this applies retrospectively.
If you would like to talk about ways to deploy OpenFaaS with faasd or licensing options for OpenFaaS Standard, we have a weekly community call every Wednesday and you're welcome to come along to talk to us there in person.
My actions before raising this issue
Why do you need this?
We are seeking guidance on deploying OpenFaaS in a Docker Compose environment that is not managed by Swarm, specifically for custom projects tailored to the needs of smaller clients.
Expected Behaviour
A feasible method to deploy OpenFaaS components using Docker Compose in Standalone Mode, allowing us to publish functions as we would in a Swarm environment.
Current Behaviour
Currently, we are unable to find documentation or examples that illustrate deploying OpenFaaS in a non-Swarm Docker Compose setup.
Are you a GitHub Sponsor (Yes/No?)
Check at: https://github.com/sponsors/openfaas
List All Possible Solutions and Workarounds
Utilizing faasd as a potential solution for deploying OpenFaaS functions via Docker Compose.
Seeking alternative methods or configurations that are not explicitly documented.
Which Solution Do You Recommend?
We are open to suggestions from the community and maintainers. If faasd is a viable option, we are willing to consider it.
Context
We are a company that has successfully integrated OpenFaaS into our SaaS project and are now looking to extend this to smaller, custom projects. We believe that using Docker Compose in Standalone Mode will help us conserve resources while still providing a robust solution for our clients.
Your Environment
docker version
(e.g. Docker 17.0.05 ):26.1.1
no
Linux 5.14.0-362.8.1.el9_3.x86_64
The text was updated successfully, but these errors were encountered: