Wrapper command on windows PS #134
Comments
|
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 |
|
Thank you for your reply. |
|
Please reopen if still an issue. |
agrski
added a commit
that referenced
this issue
Dec 2, 2022
* 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
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!
The text was updated successfully, but these errors were encountered: