1. Documentation
2. 10.2 (Latest)10.110.09.109.99.89.79.69.59.49.39.29.19.08.28.18.07.6
3. 服务器
4. Deploy
5. Docker
6. Docker image for RapidMiner Radoop Proxy

Docker image for Radoop Proxy

The documentation below describes the following Docker image:

• RapidMiner Radoop Proxy 1.2.1 (rapidminer/radoop-proxy:1.2.1)

For Docker images, seeDocker Hub.

Description

This is a RapidMiner Radoop Proxy image. It can be deployed standalone, or as part of a (container based) RapidMiner Server deployment. Learn more about Radoop Proxyhere.

For available versions, please see the tags:

• https://hub.docker.com/r/rapidminer/radoop-proxy/tags/

Authentication schemes

When co-deployed with RapidMiner Server, Radoop Proxy can use the authentication method configured within that Server deployment. When deployed standalone, only thesuperuserauthentication method is available, and the username and password used for authentication against the Radoop Proxy must be supplied when the container is provisioned. (see details below)

Environment variables

The following parameters are available:

• PORT: The port that Radoop Proxy will listen on for Radoop traffic, and route it to the Hadoop cluster. Default is1081. Please make sure the external and internal ports (from Docker perspective) are set to the same port number.
• SSL,KEYSTOREPASSWORD: ifSSLis set toon,然后加密RapidMiner年代之间的联系tudio and the Radoop Proxy. The keystore file has to be mounted as a volume to make it available for the container. It has to be mounted into the/keystore/folder, and it can be anywhere on the host computer (see examples below for more info). The keystore password can be specified inKEYSTOREPASSWORD. Disabled by default.
• AUTHENTICATION: the authentication scheme to be used. Can besuperuser,jwt, orserver. When deployed standalone, onlysuperuser法接受。默认的issuperuser.
• SCHEME,SERVERHOST,SERVERPORT: to be provided whenserverorjwtauthentication method is selected above.SCHEMEcan behttporhttps,httpis the default value. These three will provide the address of the RapidMiner Server to be used for authentication.
• SUPERUSERNAME,SUPERUSERPASSWORD: username and password to be used for authentication, whensuperuserauthentication method is selected. Defaults areproxyadminandchangeit.
• WORKERSPOOLSIZE: The number of worker threads to be used by the Radoop Proxy to handle incoming Radoop connections. Default is100.

Examples

In the following scripts, all the terms with <brackets> need to be replaced with values that are defined by you and are unique to your configuration.

Startup examples

Here's the simplest command to run Radoop Proxy, which will deploy a standalone Radoop Proxy in superuser authentication mode, with all settings on default values:

docker run \ -p 1081:1081 \ registry.www.turtlecreekpls.com/rapidminer/radoop-proxy:1.2.1

Here's an example how to deploy a Radoop Proxy which connects to an existing RapidMiner Server deployment:

docker run \ -p 1081:1081 -e AUTHENTICATION=server \ -e SERVERHOST= \ -e SERVERPORT= \ registry.www.turtlecreekpls.com/rapidminer/radoop-proxy:1.2.1

Finally, here's an example for SSL authentication enabled.

docker run \ -p 1081:1081 -e SSL=on \ -e KEYSTOREPASSWORD= \ -v :/keystore \ registry.www.turtlecreekpls.com/rapidminer/radoop-proxy:1.2.1

Example configurations for docker-compose

Here's an example how to add Radoop Proxy to an existing, secured RapidMiner Server deployment (accessible via HTTPS):

version: "3" services: proxy: image: registry.www.turtlecreekpls.com/rapidminer/radoop-proxy:1.2.1 environment: - AUTHENTICATION=server - SERVERHOST= - SERVERPORT= - SCHEME=https ports: - 1081:1081

And here's another example for a standalone Radoop Proxy listening on a non-default port:

version: "3" services: proxy: image: registry.www.turtlecreekpls.com/rapidminer/radoop-proxy:1.2.1 environment: - SUPERUSERNAME= - SUPERUSERPASSWORD= - PORT=2082 ports: - 2082:2082