Welcome to the FAQ. Here you will find a list of common questions and answers along with CLI issues you may face.
1. Does Appsody support Enterprise Windows users?
Enterprise Windows users very frequently authenticate through Azure Active Directory (AAD). In those circumstances, the Docker daemon on Windows may not be authorized to access any of the folders that are owned by the AAD user. For this reason, Appsody supports Enterprise Windows users through a workaround.
Create a new project (pick a folder that is outside of your home directory, or Docker will not have access to it).
Go into that project directory and run
appsody init <stack>
Create a new folder called
appsody init --config C:\my-appsody-config-dir\.appsody-config.yaml
Change the entry
appsody run --config C:\my-appsody-config-dir\.appsody-config.yaml
For more information on this issue, click here.
2. Why am I getting a cross-device link error on Appsody extract?
This was an issue that was faced in an older version of the software. It occurred when the Appsody CLI and the Appsody project were located on different disk volumes. If you are experiencing this problem, navigate to our GitHub page and ensure you are operating on the latest version. If you would like more information on this issue, please click here.
3. Why is Appsody deploy not displaying the URL of the Knative service?
Sometimes, when you run
appsody deploy, you may see a message that fails to provide the URL of the deployed Knative service. Although the Knative URL is not displaying, Appsody should have still been deployed successfully. This is a timing issue where
kubectl apply finishes executing before all resources have been made available.
4. Is the HTTP_PROXY environment variable used by the CLI?
Versions of Appsody at 0.2.5 and older do not support going through a HTTP proxy. However, newer versions do: Before launching Appsody, you just need to set the HTTP_PROXY or HTTPS_PROXY environment variable.