Run update.sh
This commit is contained in:
Docker Library Bot
parent
a79f230714
commit
fc404f11e6
|
|
@ -89,7 +89,7 @@ You can also use `couchdb` as the base image for your own couchdb instance and p
|
|||
Example Dockerfile:
|
||||
|
||||
```dockerfile
|
||||
FROM couchdb:latest
|
||||
FROM couchdb
|
||||
|
||||
COPY local.ini /usr/local/etc/couchdb/
|
||||
```
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ To start the Crate cluster in containers distributed to three hosts without mult
|
|||
--volume /mnt/data:/data \
|
||||
--ulimit nofile=65535 \
|
||||
--ulimit memlock=9223372036854775807 \
|
||||
crate:latest \
|
||||
crate \
|
||||
crate \
|
||||
-Des.cluster.name=crate-cluster \
|
||||
-Des.node.name=crate1 \
|
||||
|
|
|
|||
|
|
@ -0,0 +1,84 @@
|
|||
# Supported tags and respective `Dockerfile` links
|
||||
|
||||
- [`1.6.21`, `1.6`, `stable`, `latest` (*1.6/Dockerfile*)](https://github.com/eggheads/eggdrop-docker/blob/def15a99429271388c9f2958dcc1a825f729e3d3/1.6/Dockerfile)
|
||||
- [`1.8.0`, `1.8`, `develop` (*1.8/Dockerfile*)](https://github.com/eggheads/eggdrop-docker/blob/def15a99429271388c9f2958dcc1a825f729e3d3/1.8/Dockerfile)
|
||||
|
||||
[](https://imagelayers.io/?images=eggdrop:1.6.21,eggdrop:1.8.0)
|
||||
|
||||
For more information about this image and its history, please see [the relevant manifest file (`library/eggdrop`)](https://github.com/docker-library/official-images/blob/master/library/eggdrop). This image is updated via [pull requests to the `docker-library/official-images` GitHub repo](https://github.com/docker-library/official-images/pulls?q=label%3Alibrary%2Feggdrop).
|
||||
|
||||
For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see [the `eggdrop/tag-details.md` file](https://github.com/docker-library/docs/blob/master/eggdrop/tag-details.md) in [the `docker-library/docs` GitHub repo](https://github.com/docker-library/docs).
|
||||
|
||||
# What is Eggdrop?
|
||||
|
||||
Eggdrop is the world's most popular Open Source IRC bot, designed for flexibility and ease of use, and is freely distributable under the GNU General Public License (GPL). It is designed to Linux, BSD, SunOs, Windows, and Mac OS X, among others. The core codebase is extendable via TCL scripts or C modules and bots can be linked to form botnets, enabling the sharing of userfiles and partylines across multiple bots.
|
||||
|
||||
|
||||
|
||||
# How to use this image
|
||||
|
||||
## First Run
|
||||
|
||||
To run this container the first time, you'll need to pass in, at minimum, a nickname and server via Environmental Variables. At minimum, a docker run command similar to
|
||||
|
||||
```console
|
||||
$ docker run -ti -e NICK=FooBot -e SERVER=irc.freenode.net -v /path/for/host/data:/home/eggdrop/eggdrop/data eggdrop
|
||||
```
|
||||
|
||||
should be used. This will modify the appropriate values within the config file, then start your bot with the nickname FooBot and connect it to irc.freenode.net.
|
||||
|
||||
These variables are only needed for your first run- after the first use, you can edit the config file directly.
|
||||
|
||||
## Long-term Persistence
|
||||
|
||||
After running the eggdrop container for the first time, the configuration file, user file and channel file will all be available inside the container at /home/eggdrop/eggdrop/data/ . NOTE! These files are only as persistent as the container they exist in. If you expect to use a different container over the course of using the Eggdrop docker image (intentionally or not) you will want to create a persistent data store. The easiest way to do this is to mount a directory on your host machine to /home/eggdrop/eggdrop/data. If you do this prior to your first run, you can easily edit the eggdrop configuration file on the host. Otherwise, you can also drop in existing config, user, or channel files into the mounted directory for use in the eggdrop container. You'll also likely want to daemonize eggdrop (ie, run it in the background). To do this, start your container with something similar to
|
||||
|
||||
```console
|
||||
$ docker run -i -e NICK=FooBot -e SERVER=irc.freenode.net -v /path/to/eggdrop/files:/home/eggdrop/eggdrop/data -d eggdrop
|
||||
```
|
||||
|
||||
Please note that, even in daemon mode, the -i flag for docker run is required.
|
||||
|
||||
## Exposing network ports
|
||||
|
||||
If you want to expose network connections for your bot, you'll also want to use the -p flag to expose whichever port you specified in the config as the listen port (default is 3333). For example, to expose port 3333, add
|
||||
|
||||
-p 3333:3333
|
||||
|
||||
to your docker run command line.
|
||||
|
||||
## Troubleshooting / Support
|
||||
|
||||
For additional help, you can join the #eggdrop channel on Freenode
|
||||
|
||||
The git repository for the Dockerfile is maintained at https://github.com/eggheads/eggdrop-docker
|
||||
|
||||
# License
|
||||
|
||||
View [license information](https://www.gnu.org/licenses/gpl-3.0.en.html) for the software contained in this image.
|
||||
|
||||
# Supported Docker versions
|
||||
|
||||
This image is officially supported on Docker version 1.12.0.
|
||||
|
||||
Support for older versions (down to 1.6) is provided on a best-effort basis.
|
||||
|
||||
Please see [the Docker installation documentation](https://docs.docker.com/installation/) for details on how to upgrade your Docker daemon.
|
||||
|
||||
# User Feedback
|
||||
|
||||
## Documentation
|
||||
|
||||
Documentation for this image is stored in the [`eggdrop/` directory](https://github.com/docker-library/docs/tree/master/eggdrop) of the [`docker-library/docs` GitHub repo](https://github.com/docker-library/docs). Be sure to familiarize yourself with the [repository's `README.md` file](https://github.com/docker-library/docs/blob/master/README.md) before attempting a pull request.
|
||||
|
||||
## Issues
|
||||
|
||||
If you have any problems with or questions about this image, please contact us through a [GitHub issue](https://github.com/eggheads/eggdrop-docker/issues). If the issue is related to a CVE, please check for [a `cve-tracker` issue on the `official-images` repository first](https://github.com/docker-library/official-images/issues?q=label%3Acve-tracker).
|
||||
|
||||
You can also reach many of the official image maintainers via the `#docker-library` IRC channel on [Freenode](https://freenode.net).
|
||||
|
||||
## Contributing
|
||||
|
||||
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
|
||||
|
||||
Before you start to code, we recommend discussing your plans through a [GitHub issue](https://github.com/eggheads/eggdrop-docker/issues), especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.
|
||||
|
|
@ -24,7 +24,7 @@ F# (pronounced F sharp) is a strongly typed, multi-paradigm programming language
|
|||
The most straightforward way to use this image is to use it both as the build and runtime environment. In your `Dockerfile`, you can write something similar to the following:
|
||||
|
||||
```dockerfile
|
||||
FROM fsharp:latest
|
||||
FROM fsharp
|
||||
COPY . /app
|
||||
RUN xbuild /app/myproject.sln
|
||||
```
|
||||
|
|
|
|||
|
|
@ -16,10 +16,14 @@
|
|||
- [`4.2.3.4-onbuild`, `4.2.3-onbuild` (*4.2.3.4/onbuild/Dockerfile*)](https://github.com/mono/docker/blob/38858eb4bcdfc45e448ce8aae8b38148578f0f94/4.2.3.4/onbuild/Dockerfile)
|
||||
- [`4.2.4.4`, `4.2.4`, `4.2` (*4.2.4.4/Dockerfile*)](https://github.com/mono/docker/blob/763e13adbe21d4f82aae1caa066a035bd8c6d888/4.2.4.4/Dockerfile)
|
||||
- [`4.2.4.4-onbuild`, `4.2.4-onbuild`, `4.2-onbuild` (*4.2.4.4/onbuild/Dockerfile*)](https://github.com/mono/docker/blob/763e13adbe21d4f82aae1caa066a035bd8c6d888/4.2.4.4/onbuild/Dockerfile)
|
||||
- [`4.4.0.182`, `4.4.0`, `4.4`, `4`, `latest` (*4.4.0.182/Dockerfile*)](https://github.com/mono/docker/blob/e92989ade1408fd977b3a15eec3c3b7a5611bcee/4.4.0.182/Dockerfile)
|
||||
- [`4.4.0.182-onbuild`, `4.4.0-onbuild`, `4.4-onbuild`, `4-onbuild`, `onbuild` (*4.4.0.182/onbuild/Dockerfile*)](https://github.com/mono/docker/blob/09ae976880cd497a7dc9e8c89e8f26a8fcbd3879/4.4.0.182/onbuild/Dockerfile)
|
||||
- [`4.4.0.182`, `4.4.0` (*4.4.0.182/Dockerfile*)](https://github.com/mono/docker/blob/4e1d4cc196b612bcbd8466906815bfaef1f1413e/4.4.0.182/Dockerfile)
|
||||
- [`4.4.0.182-onbuild`, `4.4.0-onbuild` (*4.4.0.182/onbuild/Dockerfile*)](https://github.com/mono/docker/blob/09ae976880cd497a7dc9e8c89e8f26a8fcbd3879/4.4.0.182/onbuild/Dockerfile)
|
||||
- [`4.4.1.0`, `4.4.1` (*4.4.1.0/Dockerfile*)](https://github.com/mono/docker/blob/4e1d4cc196b612bcbd8466906815bfaef1f1413e/4.4.1.0/Dockerfile)
|
||||
- [`4.4.1.0-onbuild`, `4.4.1-onbuild` (*4.4.1.0/onbuild/Dockerfile*)](https://github.com/mono/docker/blob/dc93f0bbd9eeed6d8e0c89604f12991834a2d871/4.4.1.0/onbuild/Dockerfile)
|
||||
- [`4.4.2.11`, `4.4.2`, `4.4`, `4`, `latest` (*4.4.2.11/Dockerfile*)](https://github.com/mono/docker/blob/b2efdab5e0ef9ef0b91930956a7f5049ec0e4146/4.4.2.11/Dockerfile)
|
||||
- [`4.4.2.11-onbuild`, `4.4.2-onbuild`, `4.4-onbuild`, `4-onbuild`, `onbuild` (*4.4.2.11/onbuild/Dockerfile*)](https://github.com/mono/docker/blob/b2efdab5e0ef9ef0b91930956a7f5049ec0e4146/4.4.2.11/onbuild/Dockerfile)
|
||||
|
||||
[](https://imagelayers.io/?images=mono:3.10.0,mono:3.10.0-onbuild,mono:3.12.1,mono:3.12.1-onbuild,mono:3.8.0,mono:3.8.0-onbuild,mono:4.0.5.1,mono:4.0.5.1-onbuild,mono:4.2.1.102,mono:4.2.1.102-onbuild,mono:4.2.2.30,mono:4.2.2.30-onbuild,mono:4.2.3.4,mono:4.2.3.4-onbuild,mono:4.2.4.4,mono:4.2.4.4-onbuild,mono:4.4.0.182,mono:4.4.0.182-onbuild)
|
||||
[](https://imagelayers.io/?images=mono:3.10.0,mono:3.10.0-onbuild,mono:3.12.1,mono:3.12.1-onbuild,mono:3.8.0,mono:3.8.0-onbuild,mono:4.0.5.1,mono:4.0.5.1-onbuild,mono:4.2.1.102,mono:4.2.1.102-onbuild,mono:4.2.2.30,mono:4.2.2.30-onbuild,mono:4.2.3.4,mono:4.2.3.4-onbuild,mono:4.2.4.4,mono:4.2.4.4-onbuild,mono:4.4.0.182,mono:4.4.0.182-onbuild,mono:4.4.1.0,mono:4.4.1.0-onbuild,mono:4.4.2.11,mono:4.4.2.11-onbuild)
|
||||
|
||||
For more information about this image and its history, please see [the relevant manifest file (`library/mono`)](https://github.com/docker-library/official-images/blob/master/library/mono). This image is updated via [pull requests to the `docker-library/official-images` GitHub repo](https://github.com/docker-library/official-images/pulls?q=label%3Alibrary%2Fmono).
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ For detailed information about the virtual/transfer sizes and individual layers
|
|||
When OrientDB starts it asks for the root password. The root user is able to manage the OrientDB server: create new databases, manage users and roles. The root password can be passed to the container using an environment property:
|
||||
|
||||
```console
|
||||
$ docker run -d --name orientdb -p 2424:2424 -p 2480:2480 -e ORIENTDB_ROOT_PASSWORD=rootpwd orientdb:latest
|
||||
$ docker run -d --name orientdb -p 2424:2424 -p 2480:2480 -e ORIENTDB_ROOT_PASSWORD=rootpwd orientdb
|
||||
```
|
||||
|
||||
The [Studio](http://orientdb.com/docs/last/Home-page.html) is accessible to http://<docker-host>:2480 (e.g.: http://localhost:2480)
|
||||
|
|
@ -38,7 +38,7 @@ $ docker run -d --name orientdb -p 2424:2424 -p 2480:2480 \
|
|||
-v <databases_path>:/orientdb/databases \
|
||||
-v <backup_path>:/orientdb/backup \
|
||||
-e ORIENTDB_ROOT_PASSWORD=rootpwd \
|
||||
orientdb:latest
|
||||
orientdb
|
||||
```
|
||||
|
||||
### Running OrientDB tools
|
||||
|
|
@ -46,13 +46,13 @@ $ docker run -d --name orientdb -p 2424:2424 -p 2480:2480 \
|
|||
The OrientDB image contains a full fledge installation, so it is possible to run the [console](http://orientdb.com/docs/last/Console-Commands.html)
|
||||
|
||||
```console
|
||||
$ docker run --rm -it orientdb:latest /orientdb/bin/console.sh
|
||||
$ docker run --rm -it orientdb /orientdb/bin/console.sh
|
||||
```
|
||||
|
||||
or even the etl
|
||||
|
||||
```console
|
||||
$ docker run --rm -it -v <config_path>:/orientdb/config orientdb:latest /orientdb/bin/oetl.sh ../config/oetl-config.json
|
||||
$ docker run --rm -it -v <config_path>:/orientdb/config orientdb /orientdb/bin/oetl.sh ../config/oetl-config.json
|
||||
```
|
||||
|
||||
### Override configuration parameters
|
||||
|
|
@ -66,7 +66,7 @@ $ docker run -d --name orientdb -p 2424:2424 -p 2480:2480 \
|
|||
-v <backup_path>:/orientdb/backup \
|
||||
-e ORIENTDB_ROOT_PASSWORD=rootpwd \
|
||||
-e ORIENTDB_NODE_NAME=odb1 \
|
||||
orientdb:latest /orientdb/bin/server.sh -Ddistributed=true
|
||||
orientdb /orientdb/bin/server.sh -Ddistributed=true
|
||||
```
|
||||
|
||||
For further configuration options please refer to the [Configuration](http://orientdb.com/docs/last/Configuration.html) section of the online documentation.
|
||||
|
|
@ -78,7 +78,7 @@ Environment parameters such as heap size could be passed via command line:
|
|||
```console
|
||||
$ docker run -d --name orientdb -p 2424:2424 -p 2480:2480 \
|
||||
-e ORIENTDB_ROOT_PASSWORD=rootpwd \
|
||||
orientdb:latest /orientdb/bin/server.sh -Xmx8g
|
||||
orientdb /orientdb/bin/server.sh -Xmx8g
|
||||
```
|
||||
|
||||
# Supported Docker versions
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ $ Rscript myscript.R
|
|||
Use `r-base` as a base for your own Dockerfiles. For instance, something along the lines of the following will compile and run your project:
|
||||
|
||||
```dockerfile
|
||||
FROM r-base:latest
|
||||
FROM r-base
|
||||
COPY . /usr/local/src/myscripts
|
||||
WORKDIR /usr/local/src/myscripts
|
||||
CMD ["Rscript", "myscript.R"]
|
||||
|
|
|
|||
|
|
@ -21,28 +21,38 @@ Spiped (pronounced "ess-pipe-dee") is a utility for creating symmetrically encry
|
|||
|
||||
This image automatically takes the key from the `/spiped/key` file (`-k`) and runs spiped in foreground (`-F`). Other than that it takes the same options *spiped* itself does. You can list the available flags by running the image without arguments:
|
||||
|
||||
$ docker run -it --rm spiped
|
||||
usage: spiped {-e | -d} -s <source socket> -t <target socket> -k <key file>
|
||||
[-DFj] [-f | -g] [-n <max # connections>] [-o <connection timeout>]
|
||||
[-p <pidfile>] [-r <rtime> | -R]
|
||||
```console
|
||||
$ docker run -it --rm spiped
|
||||
usage: spiped {-e | -d} -s <source socket> -t <target socket> -k <key file>
|
||||
[-DFj] [-f | -g] [-n <max # connections>] [-o <connection timeout>]
|
||||
[-p <pidfile>] [-r <rtime> | -R]
|
||||
```
|
||||
|
||||
For example running spiped to take encrypted connections on port 8025 and forward them to port 25 on localhost would look like this:
|
||||
|
||||
$ docker run -d -v /path/to/keyfile:/spiped/key:ro -p 8025:8025 spiped -d -s '[0.0.0.0]:8025' -t '[127.0.0.1]:25'
|
||||
```console
|
||||
$ docker run -d -v /path/to/keyfile:/spiped/key:ro -p 8025:8025 spiped -d -s '[0.0.0.0]:8025' -t '[127.0.0.1]:25'
|
||||
```
|
||||
|
||||
Usually you would combine this image with another linked container. The following example would take encrypted connections on port 9200 and forward them to port 9200 in the container with the name `elasticsearch`:
|
||||
|
||||
$ docker run -d -v /path/to/keyfile:/spiped/key:ro -p 9200:9200 --link elasticsearch:elasticsearch spiped -d -s '[0.0.0.0]:9200' -t 'elasticsearch:9200'
|
||||
```console
|
||||
$ docker run -d -v /path/to/keyfile:/spiped/key:ro -p 9200:9200 --link elasticsearch:elasticsearch spiped -d -s '[0.0.0.0]:9200' -t 'elasticsearch:9200'
|
||||
```
|
||||
|
||||
If you don’t need any to bind to a privileged port you can pass `--user spiped` to make *spiped* run as an unprivileged user:
|
||||
|
||||
$ docker run -d -v /path/to/keyfile:/spiped/key:ro --user spiped -p 9200:9200 --link elasticsearch:elasticsearch spiped -d -s '[0.0.0.0]:9200' -t 'elasticsearch:9200'
|
||||
```console
|
||||
$ docker run -d -v /path/to/keyfile:/spiped/key:ro --user spiped -p 9200:9200 --link elasticsearch:elasticsearch spiped -d -s '[0.0.0.0]:9200' -t 'elasticsearch:9200'
|
||||
```
|
||||
|
||||
### Generating a key
|
||||
|
||||
You can save a new keyfile named `spiped-keyfile` to the folder `/path/to/keyfile/` by running:
|
||||
|
||||
$ docker run -it --rm -v /path/to/keyfile:/spiped/key spiped spiped-generate-key.sh
|
||||
```console
|
||||
$ docker run -it --rm -v /path/to/keyfile:/spiped/key spiped spiped-generate-key.sh
|
||||
```
|
||||
|
||||
Afterwards transmit `spiped-keyfile` securely to another host (e.g. by using scp).
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue