Is there an way to update the docker client (powershell) on windows server 2016.
When I type "docker version" in powershell, I get the following output.
Client:
Version: 1.12.0-dev
API version: 1.24
Go version: go1.5.3
Git commit: 8e92415
Built: Thu May 26 17:08:34 2016
OS/Arch: windows/amd64
Server:
Version: 20.10.9
API version: 1.41
Go version: go1.16.12m2
Git commit: 9b96ce992b
Built: 12/21/2021 21:33:06
OS/Arch: windows/amd64
I would like to use docker in the Windows Admin Console and have absolutely no idea about how I managed to install this old version in the first place.
I have already tried several times to reinstall docker, but without success.
I found out that there was an old version of the binaries under system32.
After removing them it worked.
Disclaimer: Do not try this yourself until you are 100% sure what you are doing. Be very careful with system files and folders.
Related
I am not finding any specific docs for installing Docker Community Edition o Win 2019 Server.
I downloaded a stable build from this location - https://download.docker.com/win/static/stable/x86_64/
I have extracted the folders in it, but still I am not able to run basic Docker commmands like docker --version or docker info.
If anyone can help with this?
I am using AsciidocFX version 1.7.4 to edit Asciidoc documents. When working on PlantUML diagrams and creating a syntax error, which is caused by using syntax that is not supported in older versions, I see the following message
PlantUML 1.2021.2
This version of PlantUML is 398 days old, so you should consider upgrading...
I have the following version installed on my system:
PlantUML version 1.2022.3 (Tue Mar 29 09:10:57 PDT 2022)
(GPL source distribution)
Java Runtime: OpenJDK Runtime Environment
JVM: OpenJDK 64-Bit Server VM
Obviously, AsciidocFX finds a different version. How can I configure AsciidocFX to use my latest locally install version? I went through the Settings dialogs as well as looked in the ~/.AsciidocFX-1.7.4 folder but could not find any clue.
planumtl consist of a single plantuml.jar file. You should find a plantuml-1.2021.2.jar file in your installation folder, under lib, delete it and replace it with your own version.
I'm running a solution that fails to build on Azure Pipelines on hosted agent 'macOs'.
In the log it says:
Microsoft (R) Build Engine version 15.7.224.30163 (xplat-master/d375bb6e Sat Jun 30 05:26:28 EDT 2018) for Mono
I'd like to use another version of MSBuild.
So the questions are:
1°) Can I select a version to build against?
2°) How do I know which versions are installed and available to select from?
1°) To change the version of MSBuild (as displayed in the log), I changed the version of Xamarin.
- bash: /bin/bash -c "sudo $AGENT_HOMEDIRECTORY/scripts/select-xamarin-sdk.sh $(XamarinVersion)"
displayName: Select Xamarin Version
2°) The available versions are listed in the github repo of the hosted agent image.
I build the cobalt with platform "linux-x64x11" on Ubuntu as below：
$cat /proc/version
Linux version 3.13.0-119-generic (buildd#lcy01-08) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #166-Ubuntu SMP Wed May 3 12:18:55 UTC 2017
But this Ubuntu can't not support GLES3 because coredump happens, I have to modify the src/starboard/linux/shared/gyp_configuration.gypi file, and substitute "system_gles3" with "system_gles2" to make Cobalt run successfully.
May I ask which linux distribution version support GLES3 perfectly? Otherwise I have to upgrade my opengles library in this Ubuntu.
Wait for help, thanks,
Jenson.
What is your Cobalt version? My up-to-date Cobalt on Linux falls back to GLES2 gracefully.
It looks Ubuntu 17.04 official repository does not have GLES3 yet. If you want to use GLES3, you need to manually install it. Or set the "gl_type" to "system_gles2". I recommend the latter.
I'm having this issue when committing to SourceForge using TortoiseSVN:
https://sourceforge.net/p/forge/site-support/2636/
The feedback on that page recommends using SSH to get around the problem. So, I relocated my repository to this URL per the recommendation:
svn+ssh://mikh2161#svn.code.sf.net/p/datsville/code
My username is mikh2161 and the project is called "datsville". When I try to connect it asks me for my password, which I then enter. It seems to work okay. However, the actual commit fails with this error:
Commit failed (details follow):
Stream doesn't support this capability
Polling for available data on filestream failed: Bad file descriptor
Can anyone assist me? What am I doing wrong? Thanks!
I'm running Windows 7 Pro x64.
TortoiseSVN 1.9.0, Build 26652 - 64 Bit , 2015/08/03 19:33:09
Subversion 1.9.0, -release
apr 1.5.2
apr-util 1.5.4
serf 1.3.8
OpenSSL 1.0.2d 9 Jul 2015
zlib 1.2.8
SQLite 3.8.11.1
Looks like svn+ssh support is broken in 1.9.0.
I removed that, and used 1.8.11 instead, and it worked.
This problem is caused by the Subversion client libraries for Windows. It was introduced with version 1.9.0, and the fix will be released with 1.9.1 [1] [2] . So any windows client that is using it will not work with svn+ssh. TortoiseSVN is just one example, the same was observed with JavaHL/Subclipse, SmartSVN and the Subversion command line client itself.
Update: A downgrade to version 1.8.12 (which was released along with 1.9.0) helped in my case.[3]
[1] Subversion Dev: JavaHL, 1.9: "Bad file descriptor", "Stream doesn't support this capability" errors
[2] fixed with r1696225 (there is obviously no bug filed yet)
[3] TortoiseSVN - Browse Files at SourceForge.net