I have been able to follow all the steps from this documentation up to the part where we need to initialize debug assets in VS Code Extension. I go to the Azure Dev Spaces prepare configuration option but nothing is changed under .vscode so I'm unable to debug my code in AKS directly.

Everytime I restart the project in vscode I get a message saying "Required assets to build and debug are missing from 'projectname'. Add them?". I click 'YES' but nothing happens.

Is this broken?

The first link in the readme leads to a broken hubspot page:

https://aka.ms/signup-azds -> http://landinghub.visualstudio.com/devspaces

Expired Account
The HubSpot account associated with the domain "landinghub.visualstudio.com" has expired.

Created AKS cluster and configured it to use AZDS as mentioned here.
The step "azds up" throws foll. error
"Oops... An unexpected error has occurred. A report of the error will be sent to Microsoft."

azds up -v throws same error w/o any additional logging.

Environment:
OS : Ubuntu 16:04

Able to access the AKS cluster also azds list-up works

Executing the command azds up --keep-alive --await-exec --no-telemetry (as part of debugging an application) produces the following error:

Could not locate an applicable session to keep ports and file synchronization alive.
If calling from a tool with built-in support for Azure Dev Spaces, restartthe tool.

What would be the reasons for this error? Running a normal azds up works fine.

Hi,
thje stack trace looks like this:

Starting warmup for project 'AppApi'. An error occurred during warmup for project 'AppApi': System.UnauthorizedAccessException: Access to the path 'C:\Windows\System32\config' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileSystemEnumerableIterator1.CommonInit()
at System.IO.FileSystemEnumerableIterator1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler1 resultHandler, Boolean checkHost)
at System.IO.Directory.GetDirectories(String path, String searchPattern)
at Microsoft.Mindaro.Common.IO.FileSystem.GetDirectories(String localPath, String searchPattern)
at Microsoft.Mindaro.Client.Sync.Workspace.WorkspaceSync.GetAllLocalFileItemsInner(String localRoot, String localPath, IDictionary2 items, HashSet1 ignoredDirectories, RuleResult defaultRule)
at Microsoft.Mindaro.Client.Sync.Workspace.WorkspaceSync.GetAllLocalFileItemsInner(String localRoot, String localPath, IDictionary2 items, HashSet1 ignoredDirectories, RuleResult defaultRule)
at Microsoft.Mindaro.Client.Sync.Workspace.WorkspaceSync.GetAllLocalFileItems(String localPath, IDictionary2 items) at Microsoft.Mindaro.Client.Sync.Workspace.WorkspaceSync.<Synchronize>d__21.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Mindaro.Client.Sync.SyncClient.<>c__DisplayClass23_1.<<SynchronizeAsync>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Mindaro.Client.Sync.SyncClient.<SynchronizeAsync>d__23.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClientImplementation.<SyncCodeAsync>d__32.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClientImplementation.<EnsureStartServiceForIterateAsync>d__77.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClientImplementation.<ExecuteNextIterationAsync>d__71.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClient.<ExecuteNextIterationAsync>d__19.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Client.DevSpacesServiceClient.<>c__DisplayClass26_0.<<StartDebugAsync>b__1>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.<ExecuteOperationAsync>d__2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Client.DevSpacesServiceClient.<>c__DisplayClass26_0.<<StartDebugAsync>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.<ExecuteOperationAsync>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.d__31.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.DebugService.<WarmupProjectAsync>d__24.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.<>c__DisplayClass9_0.<<ExecuteWarmupAsync>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.<ExecuteOperationAsync>d__2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.<ExecuteOperationAsync>d__2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.<ExecuteWarmupAsync>d__9.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.<>c__DisplayClass7_0.<<WarmupProject>b__3>d.MoveNext() Enabling debugging...

2019-02-11T11:27:09.1041890Z Step 6/16 : COPY ["azdevspaces/azdevspaces.csproj", "azdevspaces/"]
2019-02-11T11:27:09.1077261Z COPY failed: stat /var/lib/docker/tmp/docker-builder746045104/azdevspaces/azdevspaces.csproj: no such file or directory
2019-02-11T11:27:09.1077609Z + docker login -u azuredevopsazurecr -p xxxxxxxxxxxxx xxxxxxxxxx.azurecr.io
2019-02-11T11:27:09.1402057Z WARNING! Using --password via the CLI is insecure. Use --password-stdin.
2019-02-11T11:27:09.6082597Z WARNING! Your password will be stored unencrypted in /home/vsts/.docker/config.json.
2019-02-11T11:27:09.6084667Z Configure a credential helper to remove this warning. See
2019-02-11T11:27:09.6086110Z https://docs.docker.com/engine/reference/commandline/login/#credentials-store
2019-02-11T11:27:09.6086479Z
2019-02-11T11:27:09.6086775Z Login Succeeded
2019-02-11T11:27:09.6110024Z + docker push xxxxxxxxxxxxx.azurecr.io/azdevspaces:37282
2019-02-11T11:27:09.6501907Z The push refers to repository [azuredevopsazurecr.azurecr.io/azdevspaces]
2019-02-11T11:27:09.6503082Z An image does not exist locally with the tag: azuredevopsazurecr.azurecr.io/azdevspaces
2019-02-11T11:27:09.6522664Z + cp -r azdevspaces/charts/azdevspaces /home/vsts/work/1/a/chart
2019-02-11T11:27:09.7208434Z + mkdir -p /home/vsts/work/1/a/image
2019-02-11T11:27:09.7219517Z + echo xxxxxxxxxxxxx.azurecr.io/azdevspaces
2019-02-11T11:27:09.7219768Z + echo 37282

I would like to also delete any azure resources it created.

I have a vanilla cluster with Istio installed, and when I install Dev Spaces, then all routing within the cluster stops working. It appears that Dev Spaces is conflicting with Istio. When I uninstall Dev Spaces from the cluster, then Istio routing works perfectly.

Is this a known issue?

I am deploying a service to DevSpaces. Chart needs two yaml files, that I pass to it using install.values in azds.yaml:

install:
  chart: ../../../../k8s/helm/identity-api
  values:
  - values.dev.yaml?
  - secrets.dev.yaml?
  - inf.yaml
  - app.yaml

The first time I perform an azds up -v it works succesfully:

Using dev space 'default' with target 'edu-devspaces3'
Synchronizing files...
 Uploaded src\Services\Identity\Identity.API\app.yaml
 Uploaded src\Services\Identity\Identity.API\inf.yaml
Synchronized files in 5s
Installing Helm chart...
NAME:   default-identity-api-afb595a0
LAST DEPLOYED: Tue Jul 31 10:10:38 2018
NAMESPACE: default
STATUS: DEPLOYED

But, when I try to deploy (azds up -v again) I receive a helm error. This error is when additional app.yaml or inf.yaml are not present:

Using dev space 'default' with target 'edu-devspaces3'
Synchronizing files...
Synchronized files in 4s
Installing Helm chart...
Error: render error in "identity-api/templates/service.yaml": template: identity-api/templates/service.yaml:4:18: executing "identity-api/templates/service.yaml" at <.Values.app.svc.iden...>: can't evaluate field svc in type interface {}
Failed to install Helm chart
Service cannot be started.

If i touch (or do a dummy edit like adding a space) on both inf.yaml and app.yaml it works succesfully again (I see the files are uploaded again):

Using dev space 'default' with target 'edu-devspaces3'
Synchronizing files...
 Uploaded src\Services\Identity\Identity.API\inf.yaml
 Uploaded src\Services\Identity\Identity.API\app.yaml
Synchronized files in 4s
Installing Helm chart...
NAME:   default-identity-api-7d5fadd8
LAST DEPLOYED: Tue Jul 31 10:15:32 2018
NAMESPACE: default
STATUS: DEPLOYED

Azure Dev spaces does not seem to work for us:

Installing Helm chart...
 
NAME:   development-myapp-2e001a6b
LAST DEPLOYED: Thu Jul 26 07:36:19 2018
NAMESPACE: development
STATUS: DEPLOYED
RESOURCES:
==> v1/Service
NAME             TYPE       CLUSTER-IP    EXTERNAL-IP  PORT(S)  AGE
myapp  ClusterIP  10.0.183.246  <none>       80/TCP   1s
==> v1beta2/Deployment
NAME             DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
myapp  1        1        1           0          0s
==> v1beta1/Ingress
NAME             HOSTS                                                                      ADDRESS  PORTS  AGE
myapp  [redacted].westeurope.aksapp.io  80       0s
==> v1/Pod(related)
NAME                              READY  STATUS             RESTARTS  AGE
myapp-5896dc4f9d-vm46t  0/1    ContainerCreating  0         0s
NOTES:
1. Get the application URL by running these commands:
  [redacted].westeurope.aksapp.io/
Installed chart in 3s
 
Building container image...
Couldn't find service 'myapp' build logs after 10 minutes
Failed to build container image
Service cannot be started.

How can we fix this issue? Is there a way to increase the loglevel?

@ghogen I believe I should address this issue to you? Sorry if I'm mistaken, could you please let me know where this question/issue needs to go if not to you?

Hi.
I am trying to run one service deployment in DevSpaces. After building Dockerfile.Develop I see the following error:

Successfully built b515369330da
Built container image in 1m 49s
Waiting for container...
pods/catalogapi-69bc6c679-9ndw9: Failed: Failed to pull image "azds/devhostagent:0.1.5": rpc error: code = Unknown desc = Error response from daemon: manifest for azds/devhostagent:0.1.5 not found
pods/catalogapi-69bc6c679-9ndw9: Failed: Error: ErrImagePull
pods/catalogapi-69bc6c679-9ndw9: Failed: Error: ImagePullBackOff

I checked in dockerhub and this image (azds/devhostagent) do not have tag 0.1.5.

Note: Using the command line (azds up) deploys succesfully with no issues.

I am using:

• Azure CLI 2.0.42
• Devspaces extension: dev-spaces-preview (0.1.6)
• Azure Devspaces CLI 0.1.1918.5
• Visual Studio Tools for Kubernetes 0.20.20180725.1

I was able to debug an ASP.NET CORE web app deployed on AKS cluster the first time I enabled azure dev spaces

Now I want to debug again the same app and it doesn't work anymore.

service and deployment are created on the cluster but the pod never gets created . Last time I tried I got this error in the azure dev spaces tab

Starting warmup for project 'WebApplication1'.
Using dev space 'default' with target 'TestAks'
Release "default-webapplication1-bf1cdcbc" does not exist. Installing it now.
NAME: default-webapplication1-bf1cdcbc
LAST DEPLOYED: Thu Oct 25 18:35:09 2018
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1/Service
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
webapplication1 ClusterIP 10.0.195.68 80/TCP 1s
==> v1beta2/Deployment
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
webapplication1 1 0 0 0 1s
NOTES:

1. Get the application URL by running these commands:
   export POD_NAME=$(kubectl get pods --namespace default -l "app=webapplication1,release=default-webapplication1-bf1cdcbc" -o jsonpath="{.items[0].metadata.name}")
   echo "Visit http://127.0.0.1:8080 to use your application"
   kubectl port-forward $POD_NAME 8080:80
   Failed to build container image.
   Service cannot be started.
   An error occurred during warmup for project 'WebApplication1':
   System.InvalidOperationException: Service cannot be started.
   at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClientImplementation.d__70.MoveNext()
   --- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClient.d__21.MoveNext()
   --- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Client.DevSpacesServiceClient.<>c__DisplayClass26_0.<b__1>d.MoveNext()
   --- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.d__2.MoveNext()
   --- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Client.DevSpacesServiceClient.<>c__DisplayClass26_0.<b__0>d.MoveNext()
   --- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.d__3`1.MoveNext()
   --- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.DebugService.d__24.MoveNext()
   --- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.<>c__DisplayClass9_0.<b__0>d.MoveNext()
   --- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.d__2.MoveNext()
   --- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.d__9.MoveNext()
   --- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.<>c__DisplayClass7_0.<b__3>d.MoveNext()
   Enabling debugging...

Hi all
I'm currently hitting a roadblock when I try to debug on Azure DevSpace a blank Kubernetes Application created with File -> New Project.

The error seems to be related to my Dreamspark subscription (A "free" Azure subscription for students) which has limited capability due to its billing limitation.

Unfortunately, when VS tries to register the DevSpaces provider on this subscripton it fails and it blocks the publishing process even if I have multiple Azure Subs associated to the same account, and by the checks that I have made some already have this providere registered so should ebe visible in the drop down.

Below a screenshot of the error I get:

And how the publish window appears after clicking "Ok"

azds up fails

.NET Core 2.1 project, EastUS

An unexpected error occurred invoking 'GetServiceStatusAsync' on the server. ExecInternalServerErrorException: Operation returned an invalid status code 'BadRequest'
Service cannot be started.

I am trying to do a deploy to a Devspaces using a helm chart located in another folder. I updated the azds.json file with the correct location of the chart:

install:
  chart: ../../../../k8s/helm/catalog-api

It worked. Chart did not install because it need an additional values file located in the same folder, so I added a new entry in install.values:

  values:
  - values.dev.yaml?
  - secrets.dev.yaml?
  - ../../../../k8s/helm/inf.yaml

After adding the command azds up fails with "CommandExecuteException":

Using dev space 'default' with target 'edu-devspaces3'
Synchronizing files...Exception of type 'Microsoft.Mindaro.Client.ManagementClients.CommandExecuteException' was thrown. 

I tried (with no success):

• Use windows backslash instead of unix slash
• Use the question mark at the end

Note that If I use an invalid path in the file:

- ../../../../invalid-folder/helm/inf.yaml

I receive the error Synchronizing files...Required values file {0} not found. (so it seems is processing the path)

I'm fairly new to dev spaces, so I may be missing something very fundamental here. I cannot seem to figure out a way to support helm dependencies (requirements.yaml) together with azds. Relative references do not seem to work nor can I determine how to add a repository that the azds version of helm can see (I am prompted to execute helm repo add despite the fact that my local helm already has the referenced repository).

What is the the preferred approach to deployments that have external dependencies that aren't in the stable helm repo? Additionally, is there a document that describes the full schema for azds.yaml?

Tried to install the dev-spaces extension on a computer with only Visual Studio 2019 and it was blocked.

I've followed this quickstart and added Kubernetes/Helm support to my aspnet core project,
hit F5 in Visual Studio on Azure Dev Spaces but no DNS records got created.

I currently have a Node.js application where the main file is not server.js but actually resides at bin/www, I can change the file name in launch.json for the Launch Server (AZDS) config, however how do I change that for it to work with nodemon in the Attach to Server (AZDS) config?
I can see it still defaults to server.js even after setting the main file in package.json.

I'm not sure how to troubleshoot this issue. I have tried 2 times with different AKS clusters with the same results.

"Failed to create Azure Dev Spaces Controller 'MyAKS' in resource group 'AzureDevSpaces' in subscription 'd942ee4d-6452-47ff-afa6-99635a311dd8'.
Please include the following Request ID when contacting support: 61f3f2a4-d622-49ff-bade-27b064aa7b80"

ads controller list gives me:
Azure Dev Spaces Controllers in subscription 'd942ee4d-6452-47ff-afa6-99635a311dd8':

• Name ResourceGroup Location ProvisioningState

MyAKS AzureDevSpaces eastus Failed

Whenever I open the project from this tutorial in VSCode, using the Dev-Spaces extension, I am prompted with "Required assets to build and debug are missing from ''. Add them? - Don't Ask Again; Not Now; Yes

I click Yes but see no .vscode directory created at all and then subsequently I see:

[Azure Dev Spaces] Unable to determine the project type for ''. Please manually create the required assets to build and debug.

Hi!
I have a azds.yaml file with the following values section:

  values:
  - values.dev.yaml?
  - secrets.dev.yaml?
  - ../../../k8s/helm/inf.yaml
  - ../../../k8s/helm/app.yaml

The helm charts needs the values defined in inf.yaml and app.yaml to run succesfully, but when running azds up following error is generated:

Using dev space 'default' with target 'test-devspaces-edu'
Synchronizing files...4s
Installing Helm chart...
Helm install failed with exit code '1': Release "azds-0c712b-default-apigwmm" does not exist. Installing it now.
Error: render error in "apigwmm/templates/service.yaml": template: apigwmm/templates/service.yaml:4:18: executing "apigwmm/templates/service.yaml" at <.Values.app.svc.mobi...>: can't evaluate field svc in type interface {}

This error appears if app.yaml is not passed to the helm chart. If I copy both files to the same folder where azds.yaml file is and I change the values section to:

  values:
  - values.dev.yaml?
  - secrets.dev.yaml?
  - inf.yaml
  - app.yaml

Everything works as expected.

Note: I am using following version of azds CLI:
Azure Dev Spaces CLI (Preview)
0.1.20190207.3
API v2.13

I'm following the Get Started on Azure Dev Spaces with .NET Core and Visual Studio tutorial.

When I configured Azure Dev Spaces, then hit F5. It's usually hang my Visual Studio 2017 very long long time.

If I kill all the devenv.exe related processes and re-open VS2017 again, then Azure Dev Spaces will works smoothly.

I can use kubectl from the cli (win 10) just fine, but when I attempt to run the asp.net core 2.1 project using azure dev spaces I get the following error.

Starting warmup for project '#####'.
Waiting for namespace to be provisioned.
An error occurred during warmup for project '#####':
Autofac.Core.DependencyResolutionException: An exception was thrown while executing a resolve operation. See the InnerException for details. ---> AsyncHelpers.Run method threw an exception. (See inner exception for details.) ---> System.AggregateException: AsyncHelpers.Run method threw an exception. ---> Microsoft.Mindaro.Common.Exceptions.KubectlException: There is a problem with the Azure Dev Spaces Tools installation: Missing or invalid kubectl.exe. Please repair/reinstall and try again.
at Microsoft.Mindaro.Common.Utilities.KubectlUtilities.ValidateKubectlCanBeExecuted(ILogUtility log)
at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClientImplementation.InitializeAsync()
at Autofac.AutofacRegistrationBuilderExtensions.<>c__DisplayClass0_13.<InitializeOnActivation>b__1() at Microsoft.Mindaro.Common.Utilities.AsyncHelpers.<>c__DisplayClass0_0.<<RunSync>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject) --- End of stack trace from previous location where exception was thrown --- at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject) --- End of inner exception stack trace --- at Microsoft.Mindaro.Common.Utilities.AsyncHelpers.ExclusiveSynchronizationContext.BeginMessageLoop() at Microsoft.Mindaro.Common.Utilities.AsyncHelpers.RunSync(Func1 task)
at Autofac.AutofacRegistrationBuilderExtensions.<>c__DisplayClass0_03.<InitializeOnActivation>b__0(IActivatingEventArgs1 e)
at Autofac.Builder.RegistrationBuilder3.<>c__DisplayClass30_0.<OnActivating>b__0(Object s, ActivatingEventArgs1 e)
at Autofac.Core.Registration.ComponentRegistration.RaiseActivating(IComponentContext context, IEnumerable1 parameters, Object& instance) at Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable1 parameters)
at Autofac.Core.Resolving.InstanceLookup.b__5_0()
at Autofac.Core.Lifetime.LifetimeScope.GetOrCreateAndShare(Guid id, Func1 creator) at Autofac.Core.Resolving.InstanceLookup.Execute() at Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope, IComponentRegistration registration, IEnumerable1 parameters)
at Autofac.Core.Resolving.ResolveOperation.Execute(IComponentRegistration registration, IEnumerable1 parameters) --- End of inner exception stack trace --- at Autofac.Core.Resolving.ResolveOperation.Execute(IComponentRegistration registration, IEnumerable1 parameters)
at Autofac.Core.Lifetime.LifetimeScope.ResolveComponent(IComponentRegistration registration, IEnumerable1 parameters) at Autofac.Features.LazyDependencies.LazyRegistrationSource.<>c__DisplayClass5_11.b__1()
at System.Lazy1.CreateValue() at System.Lazy1.LazyInitValue()
at System.Lazy1.get_Value() at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClient.StartIterationTracking(ServiceIterateOption iterateOption, Func2 getTunnelPortHandler, Action1 portStatusUpdateHandler, IProgress1 progress, CancellationToken cancellationToken)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Client.DevSpacesServiceClient.EnsureIterativeSessionInitialized(String projectFilePath, IServiceConfig serviceConfig, String devSpacesConfigName)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Client.DevSpacesServiceClient.<>c__DisplayClass26_0.<b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.d__3`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.DebugService.d__25.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.<>c__DisplayClass10_0.<b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.<>c__DisplayClass8_0.<b__3>d.MoveNext()
Enabling debugging...

Does Dev Spaces support the development of non-web apps, such as background processing daemons/services?

I get an error when I try to add Kubernetes support to an existing ASP.NET web application project:

I have no more information about what is going wrong.

Trying to run sample demo https://docs.microsoft.com/en-us/azure/dev-spaces/get-started-netcore-visualstudio

It run fine from the command line azds up, but, not from Visual Studio 2017.

VS 2017 gives following error: Failed to start service 'webfrontend' in space 'default'

Running VS 2017 15.8.5
Project created in Core 2.0.

Here is the output:

An error occurred during warmup for project 'WebFrontEnd':
Microsoft.Mindaro.Common.Exceptions.DevSpacesException: Failed to start service 'webfrontend' in space 'default'.
at Microsoft.Mindaro.Client.ServiceClients.ServicesServiceClient.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClientImplementation.d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClientImplementation.d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClientImplementation.d__71.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClientImplementation.d__66.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Mindaro.Client.ManagementClients.ServiceManagementClient.d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Client.DevSpacesServiceClient.<>c__DisplayClass25_0.<b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Client.DevSpacesServiceClient.<>c__DisplayClass25_0.<b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.d__31.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.<ExecuteOperationAsync>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.DebugService.d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.<>c__DisplayClass10_0.<b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Common.Logging.PerfLoggerExtensions.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Azure.DevSpaces.Tools.Package.Services.BackgroundWarmupService.<>c__DisplayClass8_0.<b__3>d.MoveNext()

Any guidance?

I have multiple subscriptions some of which I am admin and some of which I am not, Dev Spaces is giving me the error "The current user is not authorized to register the 'Microsoft.DevSpaces' resource provider for subscription 'xxx'. Make sure that the current user has Owner or Contributor access to the subscription"

This is not the subscription I want it to use but there seems no way to change it.

Based on the videos you have made introducing Dev Spaces, it seems that the way you allow devs to replace a part of a micro services application is to intercept calls using http clients. Is there support for Azure Message Queue or any of the other message infrastructure components or is it planned at a later point? It seems to me that the usefulness of Dev Spaces going forward would be quite limited for many people if such support is not available.

Hi,

Does azds have support for deploying sidecar containers as described below?

https://kubernetes.io/blog/2015/06/the-distributed-system-toolkit-patterns/

Essentially, I am looking for ways to deploy multiple containers to the same pod.

Thanks for your help.

Hi,

I tried to follow the quickstart steps using VS17 and unfortunately I got stuck. This is what I have observed:

• AKS version is 1.10.5 (also tried with 1.10.3)
• Namespace 'azds' created (with 3 pods in it). All pods report that they're healthy.
• My quickstart MVC app got deployed successfully to the 'default' namespace (I see the pod, it reports it's healthy)
• Successful registration of my MVC app in Azure DNS
• AKS cluster is healthy (no errors/warnings, pods deployed to it work fine)
• I see an Ingress configuration for the MVC app that points to the registered DNS name
• AKS cluster is deployed to westeurope

Additional info

• I created multiple AKS clusters (using Azure CLI as well as Azure Portal wizard)
• I created multiple MVC apps and let VS Tools for K8S add dockerfile and Dev Spaces files (as described in quickstart guide)

I always end up with VS not being able to debug into the container using "Azure Dev Spaces".

MVC App container logs

λ  kubectl logs webapplication7-589b9545cb-bzx7w -c webapplication7
Info 2018-07-14T11:45:54.1801851Z agent running on 50051

VS Output when pressing "F5"

Starting warmup for project 'WebApplication7'.
Failed to get service status: Failed to get status of service 'webapplication7' in space 'default'.
Using dev space 'default' with target 'tmp9-cluster'
NAME:   default-webapplication7-201408c8
LAST DEPLOYED: Sat Jul 14 11:45:23 2018
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1/Service
NAME             TYPE       CLUSTER-IP  EXTERNAL-IP  PORT(S)  AGE
webapplication7  ClusterIP  10.0.74.75  <none>       80/TCP   1s
==> v1beta2/Deployment
NAME             DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
webapplication7  1        1        1           0          1s
==> v1beta1/Ingress
NAME             HOSTS                                                      ADDRESS  PORTS  AGE
webapplication7  webapplication7.db7a345116c24911b92d.westeurope.aksapp.io  80       1s
==> v1/Pod(related)
NAME                              READY  STATUS   RESTARTS  AGE
webapplication7-589b9545cb-bzx7w  0/2    Pending  0         0s
NOTES:
1. Get the application URL by running these commands:
  http://webapplication7.db7a345116c24911b92d.westeurope.aksapp.io/
Building container image...
Sending build context to Docker daemon  2.444MB
Step 1/12 : FROM microsoft/aspnetcore-build:2.0
 ---> 7fed40fbb647
Step 2/12 : ENV ASPNETCORE_ENVIRONMENT Development
 ---> Using cache
 ---> 85f6a63d88c8
Step 3/12 : ENV DOTNET_USE_POLLING_FILE_WATCHER true
 ---> Using cache
 ---> 25e00721ba59
Step 4/12 : EXPOSE 80
 ---> Using cache
 ---> 83424721a7d3
Step 5/12 : WORKDIR /src
 ---> Using cache
 ---> c417833e55a1
Step 6/12 : COPY WebApplication7.sln ./
 ---> Using cache
 ---> 70a6c8cd16e4
Step 7/12 : COPY WebApplication7/WebApplication7.csproj WebApplication7/
 ---> Using cache
 ---> 69af23acbaac
Step 8/12 : RUN dotnet restore -nowarn:msb3202,nu1503
 ---> Using cache
 ---> b96da181be4d
Step 9/12 : COPY . .
 ---> Using cache
 ---> b50bdecd3e73
Step 10/12 : WORKDIR "/src/WebApplication7"
 ---> Using cache
 ---> 16cd2549742e
Step 11/12 : RUN dotnet build "WebApplication7.csproj"
 ---> Using cache
 ---> f793f0995951
Step 12/12 : CMD dotnet run --no-restore --no-build --no-launch-profile
 ---> Using cache
 ---> 793671362def
Successfully built 793671362def
Built container image in 8s
Waiting for container...

Notice the error message in the second line above:

Failed to get service status: Failed to get status of service 'webapplication7' in space 'default'.

VS is stuck at the last line Waiting for container....

Response when sending a request to the MVC app's host name:

Sending a request to http://webapplication7.db7a345116c24911b92d.westeurope.aksapp.io shows:

502 Bad Gateway
nginx/1.13.12

Last Ingress controller logs

W0714 11:31:36.157594       7 controller.go:1117] unexpected error obtaining service endpoints: could not find endpoints for service default/webapplication7
W0714 11:31:36.157807       7 controller.go:775] service default/webapplication7 does not have any active endpoints
I0714 11:31:36.157925       7 controller.go:170] backend reload required
I0714 11:31:36.309684       7 controller.go:179] ingress backend successfully reloaded...
W0714 11:31:42.788356       7 controller.go:775] service default/webapplication7 does not have any active endpoints

Logs from WebApplication7 container

Info 2018-07-14T11:45:54.1801851Z agent running on 50051

I was expecting a bit more here as by default the ASP.NET Core apps created through VS template log to the console. So we should see a bunch of logs coming from the app while it's starting up ASP.NET Core.

Any suggestions how to further troubleshoot this? I'm new to Docker/K8S/AKS, so I may be missing something obvious. To me it looks like that WebApplication7 container is not properly working? However, I verified that the container works fine running locally. I also have a couple ASP.NET Core containers running in the same AKS cluster and they work fine.

Apologies for the vague issue.

Is there any way to use dev spaces without using the azds prep && azds up command under each individual application?

I can't figure out a way to be able to use dev spaces to deploy one application under multiple configurations to the same cluster, as azds prep seems to create one helm chart by default.

Consider that I want to take advantage of dev spaces' cross container debugging, but keep a declarative definition of all my services and deployments in one kube config file. Is this possible with the current release, or am I missing the point?

Using dev space 'default' with target 'DevSpaces'
Synchronizing files...10s
Installing Helm chart...The SSL connection could not be established, see inner exception.

Unsure how to see the inner exception. This is a .Net Core 2.1 project.

running
C:\WINDOWS\system32>az aks use-dev-spaces -n aksa -g aksarg

and getting

unsupported operand type(s) for |: 'DefaultStr' and 'bool'
Traceback (most recent call last):
File "C:\Users\trdai\AppData\Local\Temp\pip-install-4rn35c0b\knack\knack\cli.py", line 197, in invoke
File "C:\Users\trdai\AppData\Local\Temp\pip-install-4rn35c0b\azure-cli-core\azure\cli\core\commands_init_.py", line 336, in execute
File "C:\Users\trdai\AppData\Local\Temp\pip-install-4rn35c0b\six\six.py", line 693, in reraise
File "C:\Users\trdai\AppData\Local\Temp\pip-install-4rn35c0b\azure-cli-core\azure\cli\core\commands_init_.py", line 310, in execute
File "C:\Users\trdai\AppData\Local\Temp\pip-install-4rn35c0b\azure-cli-core\azure\cli\core\commands_init_.py", line 171, in call
File "C:\Users\trdai\AppData\Local\Temp\pip-install-4rn35c0b\knack\knack\commands.py", line 109, in call
File "C:\Users\trdai\AppData\Local\Temp\pip-install-4rn35c0b\azure-cli-core\azure\cli\core_init_.py", line 420, in default_command_handler
File "C:\Users\trdai\AppData\Local\Temp\pip-install-4rn35c0b\azure-cli-acs\azure\cli\command_modules\acs\custom.py", line 1516, in aks_use_dev_spaces
File "C:\Users\anskob.azure\cliextensions\dev-spaces-preview\azext_dev_spaces_preview\custom.py", line 38, in ads_use_dev_spaces
azds_cli = _install_dev_spaces_cli(update)
File "C:\Users\anskob.azure\cliextensions\dev-spaces-preview\azext_dev_spaces_preview\custom.py", line 118, in _install_dev_spaces_cli
should_install_azds = force_install | (not _is_dev_spaces_installed(azds_cli))
TypeError: unsupported operand type(s) for |: 'DefaultStr' and 'bool'

I have a fairly new AKS Cluster
C:\Users\mapoitra>az aks get-upgrades --name myAKS --resource-group MAPAKSDemoRG --output table
Name ResourceGroup MasterVersion NodePoolVersion Upgrades

default MAPAKSDemoRG 1.11.3 1.11.3 1.11.4

I get an error installing Dev Spaces
C:\Users\mapoitra>az aks use-dev-spaces -g MAPAKSDemoRG -n MyAKS
The installed extension 'dev-spaces-preview' is in preview.
unsupported operand type(s) for |: 'DefaultStr' and 'bool'
Traceback (most recent call last):
File "C:\Users\trdai\AppData\Local\Temp\pip-install-972ovukd\knack\knack\cli.py", line 197, in invoke
File "C:\Users\trdai\AppData\Local\Temp\pip-install-972ovukd\azure-cli-core\azure\cli\core\commands_init_.py", line 336, in execute
File "C:\Users\trdai\AppData\Local\Temp\pip-install-972ovukd\six\six.py", line 693, in reraise
File "C:\Users\trdai\AppData\Local\Temp\pip-install-972ovukd\azure-cli-core\azure\cli\core\commands_init_.py", line 310, in execute
File "C:\Users\trdai\AppData\Local\Temp\pip-install-972ovukd\azure-cli-core\azure\cli\core\commands_init_.py", line 171, in call
File "C:\Users\trdai\AppData\Local\Temp\pip-install-972ovukd\knack\knack\commands.py", line 109, in call
File "C:\Users\trdai\AppData\Local\Temp\pip-install-972ovukd\azure-cli-core\azure\cli\core_init_.py", line 420, in default_command_handler
File "C:\Users\trdai\AppData\Local\Temp\pip-install-972ovukd\azure-cli-acs\azure\cli\command_modules\acs\custom.py", line 1451, in aks_use_dev_spaces
File "C:\Users\mapoitra.azure\cliextensions\dev-spaces-preview\azext_dev_spaces_preview\custom.py", line 38, in ads_use_dev_spaces
azds_cli = _install_dev_spaces_cli(update)
File "C:\Users\mapoitra.azure\cliextensions\dev-spaces-preview\azext_dev_spaces_preview\custom.py", line 118, in _install_dev_spaces_cli
should_install_azds = force_install | (not _is_dev_spaces_installed(azds_cli))
TypeError: unsupported operand type(s) for |: 'DefaultStr' and 'bool'

When I use command az aks use-dev-spaces -g MyResourceGroup -n MyAKS got error:

Selecting Azure Dev Spaces Controller 'myAKS' in resource group 'myreoursegroup' that targets resource 'myAKS' in resource group 'myreoursegroup'...
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.Mindaro.Common.Logging.FileLogger.<.ctor>b__6_0(Object state) in E:\A\_work\581\s\src\common\Logging\Loggers\FileLogger.cs:line 32
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

azds version: Azure Dev Spaces CLI (Preview) 0.1.20181018.11

azure cli version:

azure-cli (2.0.45)                                            
                                                              
acr (2.1.4)                                                   
acs (2.3.2)                                                   
advisor (0.6.0)                                               
ams (0.2.3)                                                   
appservice (0.2.3)                                            
backup (1.2.1)                                                
batch (3.3.3)                                                 
batchai (0.4.2)                                               
billing (0.2.0)                                               
botservice (0.1.0)                                            
cdn (0.1.1)                                                   
cloud (2.1.0)                                                 
cognitiveservices (0.2.1)                                     
command-modules-nspkg (2.0.2)                                 
configure (2.0.18)                                            
consumption (0.4.0)                                           
container (0.3.3)                                             
core (2.0.45)                                                 
cosmosdb (0.2.1)                                              
dla (0.2.2)                                                   
dls (0.1.1)                                                   
dms (0.1.0)                                                   
eventgrid (0.2.0)                                             
eventhubs (0.2.3)                                             
extension (0.2.1)                                             
feedback (2.1.4)                                              
find (0.2.12)                                                 
interactive (0.3.28)                                          
iot (0.3.1)                                                   
iotcentral (0.1.1)                                            
keyvault (2.2.2)                                              
lab (0.1.1)                                                   
maps (0.3.2)                                                  
monitor (0.2.3)                                               
network (2.2.4)                                               
nspkg (3.0.3)                                                 
policyinsights (0.1.0)                                        
profile (2.1.1)                                               
rdbms (0.3.1)                                                 
redis (0.3.2)                                                 
relay (0.1.1)                                                 
reservations (0.3.2)                                          
resource (2.1.3)                                              
role (2.1.4)                                                  
search (0.1.1)                                                
servicebus (0.2.2)                                            
servicefabric (0.1.2)                                         
sql (2.1.3)                                                   
storage (2.2.1)                                               
telemetry (1.0.0)                                             
vm (2.2.2)                                                    
                                                              
Extensions:                                                   
dev-spaces-preview (0.1.6)                                    
                                                              
Python location '/opt/az/bin/python3'                         
Extensions directory '/var/lib/jenkins/.azure/cliextensions'  
                                                              
Python (Linux) 3.6.5 (default, Aug 22 2018, 23:15:02)         
[GCC 5.4.0 20160609]                                          
                                                              
Legal docs and information: aka.ms/AzureCliLegal              

I just got a new release of Visual Studio Tools for Kubernetes but I don't know what's new. Please use some tool to communicate to us what is changing.

When creating two services (frontend and webapi or whatever) you get a Host not found error when the one is calling the other that you don't get with dotnet core sdk 2.0. It seems it's not emitting the header "azds-route-as"
Could it be so?
I have a little more elaborate decription to reproduce here link

azds up fails when Dockerfile contains node:alpine image. Upon further investigation, running a kubectl logs check on the pod and container reveals this error:

k logs -n dev-space ignite2018-5d4d65c676-pf4vx -c ignite2018 Failed to load , error: Error loading shared library libintl.so.8: No such file or directory (needed by /.azds-agent/alpine/libcoreclr.so)
Failed to bind to CoreCLR at '/.azds-agent/alpine/libcoreclr.so'

If I switch to regular node image for Dockerfile, the azds up command will work.

Using latest version of DevSpaces:
Azure Dev Spaces CLI (Preview)
0.1.20181023.7

Example Dockerfile to recreate issue can be found here.

The init container gets access denied errors when trying to start zookeeper. Chart is attached, installed with the following command line.

helm upgrade --install --wait --force --debug -f ./zookeeper/values.yaml -f ./zookeeper/platform-zookeeper.yml platform-zookeeper ./zookeeper

zookeeper.zip

2019-02-11T12:38:18.3697246Z ##[section]Starting: helm upgrade mywebapi
2019-02-11T12:38:18.3702714Z ==============================================================================
2019-02-11T12:38:18.3702801Z Task : Package and deploy Helm charts
2019-02-11T12:38:18.3702906Z Description : Deploy, configure, update your Kubernetes cluster in Azure Container Service by running helm commands.
2019-02-11T12:38:18.3703003Z Version : 0.138.14
2019-02-11T12:38:18.3703052Z Author : Microsoft Corporation
2019-02-11T12:38:18.3703151Z Help : More Information
2019-02-11T12:38:18.3703218Z ==============================================================================
2019-02-11T12:38:20.4779554Z Error: path "/home/vsts/work/r1/a/drop/mywebapi/chart" not found
2019-02-11T12:38:20.4784568Z [command]/opt/hostedtoolcache/helm/2.11.0/x64/linux-amd64/helm upgrade --namespace dev --install --force --set image.repository=,image.tag= --wait mywebapi-dev /home/vsts/work/r1/a/drop/mywebapi/chart
2019-02-11T12:38:20.4844343Z ##[error]Error: path "/home/vsts/work/r1/a/drop/mywebapi/chart" not found

2019-02-11T12:38:20.4856405Z ##[section]Finishing: helm upgrade mywebapi

The last update to the Roadmap is almost a year old. Would you please update it?

Hi!

I'm getting the following error when attempting to execute an azds up on a netcore project. This initially failed using the tooling within Visual Studio, but I decided to show the output from the dev spaces CLI as it seems a bit clearer.

Waiting for container image build...Streaming build container logs for service '<SERVICE>' failed with: An unexpected error occurred invoking 'StreamBuildContainerLogsAsync' on the server. KeyNotFoundException: The given key 'spec' was not present in the dictionary. 1s

Note that the service name has been redacted.

Following this error, I am left with an inconsistent deployment. The Deployment and Service defined by the helm chart I'm referencing are created and seem intact (look as expected, no missing settings, etc), but the pod is left in a permanent waiting state as the azds pre-pull service hasn't been able to retrieve the image for it since it (apparently) failed to build. Reverting this requires manually deleting the Deployment and Service created by the chart and the related Tiller ConfigMap for this release in the azds namespace.

I tried to find something interesting about the helm charts I'm referencing (as 'spec' is a common phrase within them), but they lint without errors and work fine when used directly through our CI/CD pipeline and directly using helm. The docker images themselves also build without error outside of the azds machinery.

Not sure what other information would be helpful, but let me know what I can round up.

issue and proposal for Troubleshooting page: while creating or removing the controller from linux I'm facing the following err. Running with sudo made the trick

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.Azure.DevSpaces.Common.Logging.FileLogger.<.ctor>b__6_0(Object state) in E:\A\_work\390\s\src\common\Logging\Loggers\FileLogger.cs:line 32
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

EDIT: Also, facing similar behavior with other commands using azds (e.g. prep, up).

I would like to install the Dev Spaces tools inside my home directory on my Mac instead of modifying system paths (for a number of reasons). At first I saw no reason for the installer to use sudo to install in /usr/local/lib AND polluting my home directory with ~/lib, which is inconsistent (and feels like a cop-out).

I eventually inspected azds-osx-setup.sh and modified it to a working configuration, but it has a number of problems:

• It downloads files directly to $HOME without using an isolated temporary folder
• It runs curl with sudo multiple times, which may be construed as a security risk (and was blocked by default by my Little Snitch ruleset).
• It also runs unzip with sudo without verifying any sort of signature on the ZIP file.
• It runs sudo rm -rf on temporary files (inside $HOME!) without extensive checks (other than -w), even for deleting single files.

My suggestion is that besides fixing the above to be safer in all regards, the Mac script be changed to use ~/Library/Azure/bin (and lib) by default and that the user is directed to modifying $PATH by providing two sample lines to add to .bashrc at the end of the install - one for modifying $PATH and another for setting up bash completion.

I tried to execute Dev Space of Java Version.

If we executed the following command, automatically some file will be created.

$ azds prep --public

Especially, in this time I want to say following 3 files.

• Dockerfile
• Dockerfile.develop
• azds.yaml

As default, azds.yaml file was wrote as following.

azds.yaml : default

configurations:
  develop:
    build:
      dockerfile: Dockerfile.develop

And in order to create more small size of image, I tried to change the dockerfile to Dockerfile as follows "removed the .develop".

azds.yaml : Multi Stage Build

configurations:
  develop:
    build:
      dockerfile: Dockerfile

Then, I executed the following command, then following error was showed.

$ azds up
Using dev space 'default' with target 'yoshio-devspace'
Synchronizing files...6s
Installing Helm chart...2s
Waiting for container image build...10s
Building container image...
Step 1/12 : FROM openjdk:8-jre-slim AS base
Error parsing reference: "openjdk:8-jre-slim AS base" is not a valid repository/tag: invalid reference format
Failed to build container image.
Service cannot be started.
Service cannot be started.

In fact, the Dockerfile was wrote as Multi Stage Build.

FROM openjdk:8-jre-slim AS base
EXPOSE 8080
WORKDIR /app

FROM maven:3.5-jdk-8-slim AS build
WORKDIR /usr/src/app
COPY pom.xml .
RUN ["/usr/local/bin/mvn-entrypoint.sh", "mvn", "verify", "--fail-never"]
COPY . .
RUN ["mvn", "package"]

FROM base AS final
COPY --from=build /usr/src/app/target .
CMD ["java", "-jar", "webfrontend-0.1.0.jar"]

However, it is impossible to create the Multi Stage Build in current(latest) AKS version.
Because the Docker version is 1.13.1. As you know the Multi Stage Build was supported since 17.05. ( FeedBack Request : Increase Kubernetes node docker version to 17.05.x & +)
So I assume that the above command failed.

$ kubectl get node -o wide
NAME                       STATUS    ROLES     AGE       VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME
aks-agentpool-16231366-0   Ready     agent     3h        v1.11.3   10.240.0.5    <none>        Ubuntu 16.04.5 LTS   4.15.0-1023-azure   docker://1.13.1

If you created the Dockerfile of Multi Stage version, please write the NOTE that we will not be able to use the file now.
Actually I don't know which location is appropriate. I think that following site may be better?

https://docs.microsoft.com/en-us/azure/dev-spaces/troubleshooting

Yesterday I installed dev-spaces for the first time on my AKS cluster (which I'm using for learning and experiments, not in production)

Right after the installation everything was fine, I could debug a containerized asp.net core app from my VS2017 directly on the kubernetes cluster. This asp.net core app reads a redis cache installed also in the cluster in the form of stateful set of 3 pods with 2 containers each (redis+sentinel) the 1st pod is a redis master, the other 2 are slaves. I have used this setup for 10 days and it was working fine.

Each evening I deallocate the VMs in the cluster and restart them the morning. Kubernetes takes care of restarting all the pods. It worked for 10 days before I installed dev-spaces.

This morning when I restarted the cluster VMs redis was not working. I had plenty of connections errors in the log. Master and slaves could not communicate anymore. I restarted the pods multiple time and even recreated the whole stateful set from scratch. Nothing to do.

I noticed that dev-spaces installed an additional container in the redis pods named mindaro-proxy and reading the logs I found this container was intercepeting and closing all the communications targeting the redis containers.

I then removed dev-spaces with az aks remove-dev-spaces command and recreated the redis stateful set + pods, this time they dont have the mindaro proxy in the pod and they work fine like before.

The debugging feature is great and saves me a lot of time but then I have this bad side effect. It would be great if this problem could be solved.

Thank you

My AKS is all right and functional. Only AZDS unable to run from VS2017. It looks like a DNS problem. So weird.

Using dev space 'default' with target 'MyAKS'
Release "default-webapplication3-a5c18fa2" does not exist. Installing it now.
Error: release default-webapplication3-a5c18fa2 failed: Ingress.extensions "webapplication3" is invalid: spec.rules[0].host: Invalid value: "webapplication3.cf869ce5a6ed4c76b57f.WestUS2.aksapp.io": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
Exception when starting service on Kubernetes, Helm install failed with exit code '1': Release "default-webapplication3-a5c18fa2" does not exist. Installing it now.
Error: release default-webapplication3-a5c18fa2 failed: Ingress.extensions "webapplication3" is invalid: spec.rules[0].host: Invalid value: "webapplication3.cf869ce5a6ed4c76b57f.WestUS2.aksapp.io": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')

Start service failed.
 
Release "default-webapplication3-a5c18fa2" does not exist. Installing it now.
Error: release default-webapplication3-a5c18fa2 failed: Ingress.extensions "webapplication3" is invalid: spec.rules[0].host: Invalid value: "webapplication3.cf869ce5a6ed4c76b57f.WestUS2.aksapp.io": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
Exception when starting service on Kubernetes, Helm install failed with exit code '1': Release "default-webapplication3-a5c18fa2" does not exist. Installing it now.
Error: release default-webapplication3-a5c18fa2 failed: Ingress.extensions "webapplication3" is invalid: spec.rules[0].host: Invalid value: "webapplication3.cf869ce5a6ed4c76b57f.WestUS2.aksapp.io": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')

Service cannot be started.

Any clue?

Great work guys! Dev Spaces is absolutely amazing. I'm running into issues with PostSharp (it doesn't support MacOS or Linux).

Are there any plans to support Windows containers in Dev Spaces?