search

devspace-sh / devspace

DevSpace - The Fastest Developer Tool for Kubernetes ⚡ Automate your deployment workflow with DevSpace and develop software directly inside Kubernetes.
https://devspace.sh
Apache License 2.0
4.37k stars 361 forks source link

devspace dev command #1687

Closed sczhh closed 2 years ago

sczhh commented 3 years ago

Is this a network problem inside the container, and is there any solution?

C:\Users\appeon\source\repos\WebApplication110\WebApplication110>devspace dev
[warn]   Deploying into the 'default' namespace is usually not a good idea as this namespace cannot be deleted

[info]   Using namespace 'default'
[info]   Using kube context 'docker-desktop'
[info]   Building image '172.25.6.254:5000/webapplication110:dev' with engine 'kaniko'
[done] √ Uploaded files to container
[done] √ Build pod has started
[info]   Printing logs of pod:container devspace-build-kaniko-xmlhg:kaniko
E0926 09:00:57.825309       1 aws_credentials.go:77] while getting AWS credentials NoCredentialProviders: no valid providers in chain. Deprecated.
        For verbose messaging see aws.Config.CredentialsChainVerboseErrors
INFO[0000] Retrieving image manifest mcr.microsoft.com/dotnet/sdk:5.0-buster-slim
INFO[0000] Retrieving image mcr.microsoft.com/dotnet/sdk:5.0-buster-slim from registry mcr.microsoft.com
ERRO[0024] Error while retrieving image from cache: mcr.microsoft.com/dotnet/sdk:5.0-buster-slim Get "https://mcr.microsoft.com/v2/": dial tcp: lookup mcr.microsoft.com on 10.96.0.10:53: server misbehaving
INFO[0024] Retrieving image manifest mcr.microsoft.com/dotnet/sdk:5.0-buster-slim
INFO[0024] Retrieving image mcr.microsoft.com/dotnet/sdk:5.0-buster-slim from registry mcr.microsoft.com
error building image: Get "https://mcr.microsoft.com/v2/": dial tcp: lookup mcr.microsoft.com on 10.96.0.10:53: server misbehaving
[fatal]  error building image 172.25.6.254:5000/webapplication110:dev: error building image (Exit Code 1)
FabianKramm commented 3 years ago

@sczhh thanks for creating this issue! Yes this looks like a DNS/Network problem inside your target cluster, does it build correctly locally with docker?