Run update.sh
This commit is contained in:
parent
27c43e0a51
commit
2a79cadcd8
|
|
@ -24,9 +24,8 @@ WARNING:
|
|||
|
||||
# Supported tags and respective `Dockerfile` links
|
||||
|
||||
- [`latest`, `centos8`, `8`, `centos8.2.2004`, `8.2.2004`](https://github.com/CentOS/sig-cloud-instance-images/blob/5125788a241618b4d37254050d0bddcbd5b7df33/docker/Dockerfile)
|
||||
- [`centos8.1.1911`, `8.1.1911`](https://github.com/CentOS/sig-cloud-instance-images/blob/52cc14a6dd2efc45265417a4690964d32cf13857/docker/Dockerfile)
|
||||
- [`centos7`, `7`](https://github.com/CentOS/sig-cloud-instance-images/blob/b521221b5c8ac3ac88698e77941a2414ce6e778d/docker/Dockerfile)
|
||||
- [`latest`, `centos8`, `8`](https://github.com/CentOS/sig-cloud-instance-images/blob/12a4f1c0d78e257ce3d33fe89092eee07e6574da/docker/Dockerfile)
|
||||
- [`centos7`, `7`](https://github.com/CentOS/sig-cloud-instance-images/blob/f2788ce41161326a18420913b0195d1c6cfa1581/docker/Dockerfile)
|
||||
- [`centos6`, `6`](https://github.com/CentOS/sig-cloud-instance-images/blob/23b05f6a35520ebf338e4df918e4952830da068b/docker/Dockerfile)
|
||||
- [`centos7.8.2003`, `7.8.2003`](https://github.com/CentOS/sig-cloud-instance-images/blob/216a920c467977bbd0f456d3bc381100a88b3768/docker/Dockerfile)
|
||||
- [`centos7.7.1908`, `7.7.1908`](https://github.com/CentOS/sig-cloud-instance-images/blob/dcf7932cbda6dd9865d50bfe969927e3e1f0c671/docker/Dockerfile)
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ WARNING:
|
|||
|
||||
# Supported tags and respective `Dockerfile` links
|
||||
|
||||
- [`latest`, `base`](https://github.com/clearlinux/docker-brew-clearlinux/blob/a0891adeba8e062a71bd1b7ab1ed9113e2c5e416/Dockerfile)
|
||||
- [`latest`, `base`](https://github.com/clearlinux/docker-brew-clearlinux/blob/63e9225e1f7e2e94a9dc4970e793994c9e9391e7/Dockerfile)
|
||||
|
||||
# Quick reference (cont.)
|
||||
|
||||
|
|
|
|||
|
|
@ -24,8 +24,8 @@ WARNING:
|
|||
|
||||
# Supported tags and respective `Dockerfile` links
|
||||
|
||||
- [`2.0.0-alpha2`, `2.0`, `2`](https://github.com/composer/docker/blob/56e8b2f78eeb10669943dcddbe24d66e18c0605c/2.0/Dockerfile)
|
||||
- [`1.10.9`, `1.10`, `1`, `latest`](https://github.com/composer/docker/blob/64c8750c2acba298d218f03918e0863e8e10f6f0/1.10/Dockerfile)
|
||||
- [`2.0.0-alpha3`, `2.0`, `2`](https://github.com/composer/docker/blob/25c2d0384e6eb770dc027c83643f3ff3942fa994/2.0/Dockerfile)
|
||||
- [`1.10.10`, `1.10`, `1`, `latest`](https://github.com/composer/docker/blob/25c2d0384e6eb770dc027c83643f3ff3942fa994/1.10/Dockerfile)
|
||||
- [`1.9.3`, `1.9`](https://github.com/composer/docker/blob/268d70a1c5270dfbc89e945d40e37c0501a333f1/1.9/Dockerfile)
|
||||
|
||||
# Quick reference (cont.)
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ Consul always runs under [dumb-init](https://github.com/Yelp/dumb-init), which h
|
|||
|
||||
Running the Consul container with no arguments will give you a Consul server in [development mode](https://www.consul.io/docs/agent/options.html#_dev). The provided entry point script will also look for Consul subcommands and run `consul` as the correct user and with that subcommand. For example, you can execute `docker run consul members` and it will run the `consul members` command inside the container. The entry point also adds some special configuration options as detailed in the sections below when running the `agent` subcommand. Any other command gets `exec`-ed inside the container under `dumb-init`.
|
||||
|
||||
The container exposes `VOLUME /consul/data`, which is a path were Consul will place its persisted state. This isn't used in any way when running in development mode. For client agents, this stores some information about the cluster and the client's health checks in case the container is restarted. For server agents, this stores the client information plus snapshots and data related to the consensus algorithm and other state like Consul's key/value store and catalog. For servers it is highly desirable to keep this volume's data around when restarting containers to recover from outage scenarios. If this is bind mounted then ownership will be changed to the consul user when the container starts.
|
||||
The container exposes `VOLUME /consul/data`, which is a path where Consul will place its persisted state. This isn't used in any way when running in development mode. For client agents, this stores some information about the cluster and the client's health checks in case the container is restarted. For server agents, this stores the client information plus snapshots and data related to the consensus algorithm and other state like Consul's key/value store and catalog. For servers it is highly desirable to keep this volume's data around when restarting containers to recover from outage scenarios. If this is bind mounted then ownership will be changed to the consul user when the container starts.
|
||||
|
||||
The container has a Consul configuration directory set up at `/consul/config` and the agent will load any configuration files placed here by binding a volume or by composing a new image and adding files. Alternatively, configuration can be added by passing the configuration JSON via environment variable `CONSUL_LOCAL_CONFIG`. If this is bind mounted then ownership will be changed to the consul user when the container starts.
|
||||
|
||||
|
|
|
|||
|
|
@ -17,10 +17,10 @@ WARNING:
|
|||
# Quick reference
|
||||
|
||||
- **Maintained by**:
|
||||
[members of the Apache Flink community](https://github.com/docker-flink/docker-flink)
|
||||
[Apache Flink](https://flink.apache.org/community.html#people)
|
||||
|
||||
- **Where to get help**:
|
||||
[Community & Project Info](https://flink.apache.org/community.html)
|
||||
[Official Apache Flink Mailing lists](https://flink.apache.org/community.html#mailing-lists) and [StackOverflow (tag `apache-flink`)](https://stackoverflow.com/questions/tagged/apache-flink)
|
||||
|
||||
# Supported tags and respective `Dockerfile` links
|
||||
|
||||
|
|
@ -34,7 +34,7 @@ WARNING:
|
|||
# Quick reference (cont.)
|
||||
|
||||
- **Where to file issues**:
|
||||
[https://github.com/docker-flink/docker-flink/issues](https://github.com/docker-flink/docker-flink/issues)
|
||||
https://issues.apache.org/jira/browse/FLINK
|
||||
|
||||
- **Supported architectures**: ([more info](https://github.com/docker-library/official-images#architectures-other-than-amd64))
|
||||
[`amd64`](https://hub.docker.com/r/amd64/flink/)
|
||||
|
|
@ -52,87 +52,13 @@ WARNING:
|
|||
|
||||
# What is Apache Flink?
|
||||
|
||||
Apache Flink is an open source stream processing framework with powerful stream- and batch-processing capabilities.
|
||||
|
||||
Learn more about Flink at [https://flink.apache.org/](https://flink.apache.org/)
|
||||
|
||||
> [wikipedia.org/wiki/Apache_Flink](https://en.wikipedia.org/wiki/Apache_Flink)
|
||||
[Apache Flink](https://flink.apache.org/) is an open source stream processing framework with powerful stream- and batch-processing capabilities.
|
||||
|
||||

|
||||
|
||||
# Flink Docker image tags
|
||||
# How to use Apache Flink with Docker?
|
||||
|
||||
Starting with Flink 1.5, images without "hadoop" in the tag are the "Hadoop-free" variant of Flink. If you require Hadoop support (such as its HDFS filesystem implementation), you should reference an image whose tag includes the Hadoop version you need.
|
||||
|
||||
# How to use this Docker image
|
||||
|
||||
## Running a JobManager or a TaskManager
|
||||
|
||||
You can run a JobManager (master).
|
||||
|
||||
```console
|
||||
$ docker run --name flink_jobmanager -d -t flink jobmanager
|
||||
```
|
||||
|
||||
You can also run a TaskManager (worker). Notice that workers need to register with the JobManager directly or via ZooKeeper so the master starts to send them tasks to execute.
|
||||
|
||||
```console
|
||||
$ docker run --name flink_taskmanager -d -t flink taskmanager
|
||||
```
|
||||
|
||||
## Running a cluster using Docker Compose
|
||||
|
||||
With Docker Compose you can create a Flink cluster:
|
||||
|
||||
```yml
|
||||
version: "2.1"
|
||||
services:
|
||||
jobmanager:
|
||||
image: ${FLINK_DOCKER_IMAGE_NAME:-flink}
|
||||
expose:
|
||||
- "6123"
|
||||
ports:
|
||||
- "8081:8081"
|
||||
command: jobmanager
|
||||
environment:
|
||||
- JOB_MANAGER_RPC_ADDRESS=jobmanager
|
||||
|
||||
taskmanager:
|
||||
image: ${FLINK_DOCKER_IMAGE_NAME:-flink}
|
||||
expose:
|
||||
- "6121"
|
||||
- "6122"
|
||||
depends_on:
|
||||
- jobmanager
|
||||
command: taskmanager
|
||||
links:
|
||||
- "jobmanager:jobmanager"
|
||||
environment:
|
||||
- JOB_MANAGER_RPC_ADDRESS=jobmanager
|
||||
```
|
||||
|
||||
and just run `docker-compose up`.
|
||||
|
||||
Scale the cluster up or down to *N* TaskManagers:
|
||||
|
||||
```console
|
||||
docker-compose scale taskmanager=<N>
|
||||
```
|
||||
|
||||
## Configuration
|
||||
|
||||
These are the default ports used by the Flink image:
|
||||
|
||||
- The Web Client is on port `8081`
|
||||
- JobManager RPC port `6123`
|
||||
- TaskManagers RPC port `6122`
|
||||
- TaskManagers Data port `6121`
|
||||
|
||||
# About this repository
|
||||
|
||||
This repository is available on [github.com/docker-flink/docker-flink](https://github.com/docker-flink/docker-flink), and the official build is on the [Docker Hub](https://hub.docker.com/_/flink/).
|
||||
|
||||
This repository is maintained by members of the Apache Flink community.
|
||||
Please refer to the official [Apache Flink documentation](https://ci.apache.org/projects/flink/flink-docs-master/) about [how to use Apache Flink with Docker](https://ci.apache.org/projects/flink/flink-docs-master/ops/deployment/docker.html).
|
||||
|
||||
# License
|
||||
|
||||
|
|
@ -140,7 +66,7 @@ Licensed under the Apache License, Version 2.0 (the "License"); you may not use
|
|||
|
||||
https://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Apache Flink, Flink®, Apache®, the squirrel logo, and the Apache feather logo are either registered trademarks or trademarks of The Apache Software Foundation.
|
||||
Apache Flink, Flink®, Apache®, the squirrel logo, and the Apache feather logo are either registered trademarks or trademarks of [The Apache Software Foundation](https://apache.org/).
|
||||
|
||||
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ WARNING:
|
|||
|
||||
# Supported tags and respective `Dockerfile` links
|
||||
|
||||
- [`1.4.3-alpine3.11`, `1.4-alpine3.11`, `1-alpine3.11`, `latest`](https://github.com/dshearer/jobber-docker/blob/f7b276c7e49184667f6fc7323e15735c3a08c1d2/alpine3.11/Dockerfile)
|
||||
- [`1.4.4-alpine3.11`, `1.4-alpine3.11`, `1-alpine3.11`, `latest`](https://github.com/dshearer/jobber-docker/blob/cd07d76987097b5389aa9be5f48df041aa74d699/alpine3.11/Dockerfile)
|
||||
|
||||
# Quick reference (cont.)
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue