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 has been archived by the owner on Jun 13, 2021. It is now read-only.
I notice that docker app 0.8 is now out of release candidate and supported by non-edge installs of docker-ce. In order to make docker app accessible to less technical audiences, it would be extremely helpful to have a more streamlined install experience which does not require PowerShell on Windows.
Would it be possible to publish the install scripts to a package manager such as chocolatey.org (for Windows) and brew.sh (for Mac)? Or alternatively, something like docker plugin install docker-app?
The docker app interface gives us developers a way to reach less-technical audiences who are not comfortable managing docker-compose files or multiple CLI args. I'd like to reach these users (or at least start to pilot to them, but I feel that I will quickly become blocked by the install experience as it exists today.
Any assist, roadmap features, or ideas to streamline?
Thanks!
Steps to reproduce the issue:
Search for instructions to install docker app (specifically for windows but similarly for mac).
Describe the results you received:
Instructions requires running advanced commands through powershell, preceeded by either customization of Docker settings through a UI or via an environment variable which would need to be set globally.
Describe the results you expected:
Would love to have a simpler "one-step" install experience which I can share with non-technical audiences who can benefit from docker apps but are not yet familiar with docker.
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Docker version 19.03.5, build 633a0ea
Output of docker app version:
Version: v0.8.0
Git commit: 7eea32b7
Built: Tue Jun 11 20:53:26 2019
OS/Arch: windows/amd64
Experimental: off
Renderers: none
Invocation Base Image: docker/cnab-app-base:v0.8.0
I'd like to reach these users (or at least start to pilot to them, but I feel that I will quickly become blocked by the install experience as it exists today.)
Same.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I notice that docker app 0.8 is now out of release candidate and supported by non-edge installs of
docker-ce
. In order to make docker app accessible to less technical audiences, it would be extremely helpful to have a more streamlined install experience which does not require PowerShell on Windows.Would it be possible to publish the install scripts to a package manager such as chocolatey.org (for Windows) and brew.sh (for Mac)? Or alternatively, something like
docker plugin install docker-app
?The
docker app
interface gives us developers a way to reach less-technical audiences who are not comfortable managing docker-compose files or multiple CLI args. I'd like to reach these users (or at least start to pilot to them, but I feel that I will quickly become blocked by the install experience as it exists today.Any assist, roadmap features, or ideas to streamline?
Thanks!
Steps to reproduce the issue:
Search for instructions to install docker app (specifically for windows but similarly for mac).
Describe the results you received:
Instructions requires running advanced commands through powershell, preceeded by either customization of Docker settings through a UI or via an environment variable which would need to be set globally.
Describe the results you expected:
Would love to have a simpler "one-step" install experience which I can share with non-technical audiences who can benefit from docker apps but are not yet familiar with docker.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version
:Output of
docker app version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
n/a
The text was updated successfully, but these errors were encountered: