Closed darren-rdy closed 6 months ago
Hi Freddy, Please let me know if you need any more information. Really appreciate the work you put into this package. Cheers, Darren.
In this case, it is trying to create a winrm user inside the container and prepare the container for a connection. I will investigate why this doesn't work - why the PW doesn't meet domain requirements??? Could you tell me what the value if this:
(Get-CimInstance win32_ComputerSystemProduct).UUID
is on your machine?
UUID on the Docker host machine is 03000200-0400-0500-0006-000700080009
The container is not domain joined, so surely it's not trying to check my actual domain password policy?
Thanks Under PS5 as administrator, you can connect to the container with no authentication. Running PS5 as non-admin or PS7 - this doesn't work, so I create a user inside the container and use the UUID from the host as password - obviously the UUID is not a very secure password, but it is only for connections from the host. So, your UUID doesn't meet the password requirements inside of the container. I will fix this by modifying the password generation - and also allow people to set tryWinRmSession configuration to false in order to avoid winrm altogether.
Expect a new ContainerHelper later today with these fixes.
please test the latest preview, which should have a fix for this.
Thanks Freddy - confirmed working
PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue When creating a new container, an error is returned that stops the container initialisation: Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain
Scripts used to create container and cause the issue
Full output of scripts
Screenshots N/A
Additional context