Plastic Client not working (correctly) in a docker (windows) container

[EEwert]

I have the 10.0.16.5397 client installed in a docker for windows container. Everything seems to work except that the result of cm update is a workspace with ONLY directories and zero files.  

The same MSI (10.0.16.5397) on a VM hosting the container works correctly. This also happens within the container if the workspace is located on a mounted volume (i.e. NOT "in" the container).

Is there something "extra special" that I am missing to run cm.exe inside a docker container (Windows)?

info:

PlasticSCM
10.0.16.5397
https://s3.eu-west-2.amazonaws.com/plastic-releases/releases/10.0.16.5397/plasticscm/windows/PlasticSCM-10.0.16.5397-windows-cloud-installer.exe

Windows Server 2019 Datacenter
10.0.17763.0
mcr.microsoft.com/windows/servercore:ltsc2019

 

[EEwert]

OK, I am fairly certain it is because of the Encryption key missing.  (When I ran the UI the dialog box popped up on a VM that was "fresh".)

How do I set the Encryption key for the command line tools? (without a UI!)

[Héber]

Hi, 

You can create a cryptedservers.conf and the correspondent .key file with the password and place it under the local config folder (~/.plastic4). That way, Plastic will try to use it there. 

Another option is to simply copy them from another machine.

 

Best,

Héber.