Container is not published to MCR (was: Unable to generate Alarms)

[azure-samples]

Container is not published to MCR (was: Unable to generate Alarms)

[buzzfrog]

I tested with the following command:
docker run --rm -it -p 60000:60000 -p 8080:8080 --name opcplc mcr.microsoft.com/iotedge/opc-plc:latest --pn=60000 --autoaccept --nospikes --nodips --nopostrend --nonegtrend --nodatavalues --sph --sn=25 --sr=5 --st=uint --fn=5 --fr=1 --ft=uint --ctb --alm

And from my point of view, it works,

[luiscantero]

@jaypaddy this should be working now, please confirm, thanks. CC @buzzfrog

[buzzfrog]

Strange,
My understanding was that --alm is included in the version 1.2.3. The version you are testing is 1.2.2.3.
Let's investigate

[buzzfrog]

Hi again
I tested the latest version locally with your parameters and it works.
--autoaccept --nospikes --nodips --nopostrend --nonegtrend --nodatavalues --sph --sn=25 --sr=5 --st=uint --fn=5 --fr=1 --ft=uint --ctb --alm

Maybe this hasn't been built as a container yet?
BTW: When using --ctb you should see new nodes as children of Server: Green and Yellow

[hansgschossmann]

Sorry about this. I think the reason is that our team has done restructuring of the MCR publishing process and i had no chance yet to adjust opcplc.
Local build should work. I will look into the MCR problem and resolve it as part of this issue.

[jaypaddy]

Sorry for the delay. I deleted the previous version and ran the command as put in by @buzzfrog its up and running with the --alm option. Thank you.