Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Wrapper command on windows PS #134

Closed
sudham opened this issue Apr 8, 2018 · 3 comments
Closed

Wrapper command on windows PS #134

sudham opened this issue Apr 8, 2018 · 3 comments

Comments

@sudham
Copy link

sudham commented Apr 8, 2018

I need to run this on windows PS -
docker run -v $(pwd):/model seldonio/core-python-wrapper:0.7 /model IrisClassifier 0.1 seldonio --force
The error I get is "invalid reference format". What is the correct command ? Appreciate if some help - am new to docker and kubernetes but managed to get this far!
@ukclivecox
Copy link
Contributor

Can you tell us which example you are running? And which steps you have done?

Did you download the Windows version of s2i? https://github.com/openshift/source-to-image/releases/tag/v1.1.9a

@sudham
Copy link
Author

sudham commented Apr 9, 2018

Thank you for your reply.
I am using the Windows releases -- sklearn_iris example.
I got past the above problem by replacing the (pwd) with {pwd}. Now the error I get is this -
Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates
Am not sure if it was v1.1.9a or v1.1.9.

@ukclivecox
Copy link
Contributor

Please reopen if still an issue.

agrski added a commit that referenced this issue Dec 2, 2022
@agrski
Add Docker setup for data-flow engine (#134)
fcfb971 
* Remove erroneous symlink

* Fix symlinks for generated JVM Protobuf files

* Add WIP Dockerfile for data-flow engine

This checkpoints a working Gradle build within the image.
Running the engine as an application is still to do.

* Add JRE/runtime stage to Dockerfile

* Add main class to JAR manifest in build.gradle

* Build fat JAR as default for application

* Add TODO for configuration in data-flow engine

* Add container CMD for data-flow engine

* Explain switch from Alpine to Debian for Zulu builder vs. runner images

* Add TODOs for data-flow engine Dockerfile

* Fix typo in env var prefix for CLI args

* Add Docker build/push dataflow engine Make targets

* Add dataflow engine local run Make target

* Add missing PHONY annotations to Makefile targets

* Add dataflow engine service to base Compose manifest

* Refactor Kafka image & ports to vars for Compose base manifest

* Use Kafka port var for dataflow engine env vars in Compose manifest

* Remove trailing whitespace

* Reorder services to be alphabetical in Compose host manifest

* Remove unnecessary TODO

The dataflow engine supports arguments via env vars,
which is easier than also adding CLI argument handling for containerised
environments such as Docker and k8s.

* Remove done/in-progress TODO

* Refactor definition of dataflow's upstream host into internal/host manifests for Compose

* Add bridge & host dataflow engine Compose targets in Makefile

* Remove Compose dependencies for dataflow engine

The service dependency management in Compose defines an order in which to start containers,
but has no notions of readiness.
It is better to fix the dataflow engine to retry its connection to the upstream (scheduler),
rather than relying on the off-chance of a fast container start-up.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sudham @ukclivecox