-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft container entry are not the newest release #11
Comments
Hi! I noticed the same issue on my end. Basically i would like to use the --Nodesfile parameter but it is not available on the lattest docker image. Would be Possible to make thsi version public? |
@pcbl Until they decide to publish a newer version, you can set up your own container registry in azure, and publish this module there yourself form VSCode or VS. |
@Swampen , sure thing. Already working on it. It would just be so convenient when it was already there. :-) |
PR #23 fixed this |
There was an issue in the build scripts which is fixed and latest is now the latest version (1.1.6) |
This issue is for a: (mark with an
x
)Minimal steps to reproduce
Any log messages given by the failure
Expected/desired behavior
OS and Version?
Mention any other details that might be useful
The image on mcr.microsoft.com/iotedge/opc-plc should be updated to the newest release
The text was updated successfully, but these errors were encountered: