Azure VM Agent Status not ready
I have created a red hat openshift private cluster but the VMS are stuck in the state of "agent status not ready." I have followed these troubleshooting steps: Linux Virtual Machine Agent Status "Not Ready" - Microsoft Community Hub However, all of them seem to point to trying to check and see what is on the VM itself. I am unable to do this because I can't SSH into the machine. Has anyone else ran into this issue and been able to resolve it? I am deploying it via CLI as I was not able to do it via GUI for some reason. This is my script: #az login az account set --name "accountnamehidden" #az provider register -n Microsoft.RedHatOpenShift --wait #az provider register -n Microsoft.Compute --wait #az provider register -n Microsoft.Storage --wait #az provider register -n Microsoft.Authorization --wait $LOCATION= "eastus" # the location of your cluster $RESOURCEGROUP= "sample-rg" # the name of the resource group where you want to create your cluster $CLUSTER= "K8sDev1test" # the name of your cluster $arovnet= "sample-vnet" $mastersubnet = "k8sDev1-master-ue-snet" $workersubnet = "k8sDev1-worker-ue-snet" az aro create --resource-group "samplerg" --vnet-resource-group "sample-vnet-rg" --name $CLUSTER --vnet $arovnet --master-subnet "k8sDev1-master-ue-snet" --worker-subnet "k8sDev1-worker-ue-snet" --apiserver-visibility Private --ingress-visibility Private --fips true --outbound-type UserDefinedRouting --client-id hidden --client-secret hidden
Bring PowerShell native CLI for Windows container management (docker cli)
ITNOA I think integration and consistency is key value for one ecosystem, so I think Microsoft must be provide native PowerShell CLI (cmdlet) for management and using windows container instead of using Linux like CLI (docker cli), this approach have many benefits into automation tools based on PowerShell and can promote this ecosystem and make many goods for DevOps and Sysadmins to achieve Objective Oriented view of container management and usage. Unfortunately this repo https://github.com/microsoft/Docker-PowerShell is dead and stop development, please reopen this repo and make active development to this module Microsoft PowerShell is the main shell of the Windows Server so we expect we can use Windows Container with PowerShell native cmdlet instead of Linux like cli (docker cli) thanks
LCOW guide for windows server 2019
Hello Ppl, I have been trying to use linux container on windows (2019 server). I have found any straight forward guide which would direct me how to use this feature on windows 2019 server. I think in the announcement it was mentioned windows 2019 server would be able to run Linux containers. I have tried to use both version of Docker EE the standard and preview version. It will be great help if someone has or know right steps to run LCOW and Windows containers simultanously Appreciate a repsonse. Thanks
On Windows Server 2017 docker plugin list command error out
hi all My Environment : Windows 2016 Docker v 18.03 I executed "docker plugin list" command on cmd and it displayed following error message “Error response from daemon: plugins are not supported on this platform” is docker plugin not supported officially on Windows 2016/2019 ? is there any plan to add suppor for this ? thank you in advance. Regards Vidhut
How do I run Sql for Linux with LCOW enabled in Docker EE?
I installed the EE preview on a 1709 server core VM: Server Version: 17.10.0-ee-preview-3 Storage Driver: windowsfilter (windows) lcow (linux) LCOW is enabled. I am unable to run the mssql-server-linux image because it needs 2GB of RAM: PS C:\smotest> docker run -e “ACCEPT_EULA=Y” -e “SA_PASSWORD=mypassword101” -h sqlserver --name sqlserver -p:1433 --isolation hyperv -m 4GB --rm microsoft/mssql-server-linux sqlservr: This program requires a machine with at least 2000 megabytes of memory. If I run the base ubuntu image, top reports less than 1 GB total mem. How do I force the container to be big enough for SQL to run?
