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
{{ message }}
This repository was archived by the owner on Jul 18, 2025. It is now read-only.
**Note:** To use Application Packages as images (i.e.: `save`, `push`, or `deploy` when package is not present locally) on Windows, one must be in Linux container mode.
162
162
163
-
## Integrating with Helm
164
-
165
-
`docker-app` comes with a few other helpful commands as well, in particular the ability to create Helm Charts from your Docker Applications. This can be useful if you're adopting Kubernetes, and standardising on Helm to manage the lifecycle of your application components, but want to maintain the simplicity of Compose when writing you applications. This also makes it easy to run the same applications locally just using Docker, if you don't want to be running a full Kubernetes cluster.
166
-
167
-
```
168
-
$ docker-app helm
169
-
```
170
-
171
-
This will create a folder, `<my-application-name>.chart`, in the current directory. The folder contains the required `Chart.yaml` file and templates describing the `stack` Kubernetes object based on the Compose file in your application.
172
-
173
-
_Note that this requires the Compose Kubernetes controller available in Docker for Windows and Docker for Mac, and in Docker Enterprise Edition._
174
-
175
-
### Helm chart for Docker EE 2.0
176
-
177
-
In order to create a helm chart that is compatible with version 2.0 of Docker Enterprise Edition, you will need to use the `--stack-version` flag to create a compatible version of the helm chart using `v1beta1` like so:
178
-
179
-
```bash
180
-
$ docker-app helm --stack-version=v1beta1
181
-
```
182
-
183
163
## Single file or directory representation
184
164
185
165
If you prefer having the three core documents in separate YAML files, omit the `-s` / `--single-file` option to
@@ -213,22 +193,6 @@ All `docker-app` commands accept an image name as input, which means you can run
213
193
$ docker-app inspect myhubuser/hello
214
194
```
215
195
216
-
## Forking an existing image
217
-
218
-
Found an app on a remote registry you'd like to modify to better suit your needs? Use the `fork` subcommand:
This command will create a local, editable copy of the app on your system. By default, the copy is created inside the current directory; you may use the `--path` flag to configure a different destination.
225
-
226
-
For example, the following will create the `/opt/myapps/hello2.dockerapp` folder containing the forked app's files:
We have lots of ideas for making Compose-based applications easier to share and reuse, and making applications a first-class part of the Docker toolchain. Please let us know what you think about this initial release and about any of the ideas below:
@@ -264,8 +228,6 @@ Options:
264
228
Commands:
265
229
completion Generates completion scripts for the specified shell (bash or zsh)
266
230
deploy Deploy or update an application
267
-
fork Create a fork of an existing application to be modified
268
-
helm Generate a Helm chart
269
231
init Start building a Docker application
270
232
inspect Shows metadata, settings and a summary of the compose file for a given application
271
233
merge Merge a multi-file application into a single file
0 commit comments