At first Vscode was running perfectly.
But suddenly after some days VScode is not working.
I am connected to my wifi but VScode shows
I have uninstalled Vscode and all the related directories but it was helpless.
Help would be appreciated.
I had the same issue with me for some time.It was a issue with the proxy i used before.
Solution:
Goto Environment Variables Settings in windows and remove the variable with the proxy address.
good luck!
Related
I've been regularly using the Tabnine VSCode extension on my computer for a while now, and it's been very helpful so far. However, I'm having trouble installing it inside a DevContainer.
Outside the DevContainer, Tabnine works perfectly fine.
On the other hand, although I've installed Tabnine as an extension in the DevContainer, inside the DevContainer
there are no suggestions being made, typing tabnine::config does nothing, and there's no TabNine icon in the Activity Bar.
I've tried adding port forwarding to port 5555, but VSCode automatically changes it to port 5556, and it doesn't fix the issue.
Is there anything I can do to get TabNine working in my DevContainer? I'm still very much a beginner, so I apologize if I'm missing something obvious.
If you are using M1 chip then try to force build docker image with flag "--platform linux/amd64". Tabnine will run just fine
You don't need to install Tabnine extension in the devcontainer. Only install it in the Host instance and the devcontainer will auto do the port forwarding for you.
Tested with version of Tabnine v3.5.45
I am using test containers library to launch a container. It worked for a while but currently running into this
java.lang.IllegalStateException: Could not connect to Ryuk at localhost:49167
at org.testcontainers.utility.ResourceReaper.start(ResourceReaper.java:201)
at org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:205)
at org.testcontainers.LazyDockerClient.getDockerClient(LazyDockerClient.java:14)
at org.testcontainers.LazyDockerClient.authConfig(LazyDockerClient.java:12)
at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:310)
I looked at the resource reaper code and it seems like it is failing here
public synchronized void performCleanup() {
this.registeredContainers.forEach(this::stopContainer);
this.registeredNetworks.forEach(this::removeNetwork); //FAILS HERE
this.registeredImages.forEach(this::removeImage);
}
I can confirm that this is resolved by updating testcontainers to 1.16.0 version
Was facing the same exception with testcontainers 1.15.3
Windows 10, Docker desktop 4.0.0
I tried everything mentioned here but nothing worked.
if anyone is still facing the issue they can give this one a try...this worked for me
this works for windows
open you power shell in administrator mode.
run "net stop winnat"
run "net start winnat"
doing this resolved this issue on my setup. hope this helps someone
I ran into the same issue. Same Docker-for-Mac version.
Solution for me was to disable "Use gRPC FUSE for file sharing" in Preferences:
For me, restarting the local docker engine solved the problem
I'm on a Windows 11 machine with the same issue:
It turned out that a vast number of ports were allocated by the service "IP helper" (relates to ipv6 support), i.e. ports prior allocated by testcontainers, or other services. They were allocated for weeks by Ip helper but never, or rarely, released. By permanently disabling service Ip helper all issues were resolved and the set-up works great since then without any observed side effects that I am in need of.
Setting: Windows11 + Rancher Desktop
Restarting Rancher Desktop did not help. However, restarting my computer did the job.
I have a bunch of containers running .Net Framework Apps on Windows Containers. Apps work great, containers work perfectly. I need to debug some code on one of the containers using VS2019 and according to this article it should be easy https://learn.microsoft.com/en-us/visualstudio/debugger/attach-to-process-running-in-docker-container?view=vs-2019
Unfortunately, I only see "Docker (Linux Container)". I do not see an option for "Docker (Windows Container)" and I don't see any additional steps needed in the articles or any other to enable this.
I can confirm that my Docker Desktop is switched to Windows Container and everything is working perfectly I just don't see this option but seems like I should be able to. Has anyone come across this and found a solution? I saw some stuff for installing a remote debugger on the container but again the article does not say this is a prerequisite. Any help will be much appreciated.
Thanks,
To anyone facing the same issue, the answer is to upgrade your visual studio 2019 instance to the latest. I noticed I was on 16.4.x. I upgraded to 16.8.3 and the options all appeared and worked as expected. Apparently the options for Windows containers and the new WSL 2 based engine are only available in 16.5.x and above. Hope this helps someone out.
I'm using Docker on Itellij ultimate on Windows 10 home, however I met this problem when using command docker ps. Can any one tell me how to solve this problem?
docker_engine: The system cannot find the file specified is a general connectivity error to the service. Most likely related to the desktop app not being running. So make sure it's in the tray icon up and running, otherwise restart it. Otherwise, check the firewall and antivirus for any block rules.
I know this question is asked before but I could not find any right solution for that
I have install jenkins on my windows 7 as windows service, it works fine with default URL localhost:8080, but when I set //mycomputerName:8080 in configuration system- jenkins location and then save it and restarted jenkins and enter //mycomputerName:8080 in browser address jenking will not open. I have done the same installation on my laptop windows 7 without any problem, but on my desktop I have installed, uninstalled several times with the same problem.
I just want to give my solution
Go to Jenkins Home Directory ( I have mine in C:\Jenkins)
Edit jenkins.xml
Add this --prefix=/jenkins to the end of the argument as show below and restart the jenkins service ALL worked OK for me !
Example :
<arguments>-Xrs-Xmx256mDhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "%BASE%\jenkins.war" --httpPort=8080 --prefix=/jenkins</arguments>
Open Url http://localhost:8080/jenkins this should bring up the home page of jenkins
As I said in my question above many people have asked this question and had the same problem but all answer have been something from jenkins documentation and actually not solution.
so finally I found the problem and write it here probably for some people with the same problem
first I uninstalled jenkins removed all files, folder and everything related to jenking also from windows registry and installed jenking but did not work.
reinstalled windows (upgrade) and installed jenking again but did not work.
next I clean reinstalled windows and installed jenkins and in this case jenkins works as I expected but I do not know what was wrong with the windows.
Add to Vamshi's answer. Instead of the config in the
C:\Users\XXXX\AppData\Local\Jenkins\.jenkins\config.xml (you won't find <argument> in this file)
add the --prefix=\jenkins to the <argument> in jenkins.xml
C:\Program Files\Jenkins and restart the service.