Run update.sh

This commit is contained in:
Docker Library Bot 2017-02-28 16:32:53 -08:00
parent c8164569c7
commit 63a95881df
4 changed files with 83 additions and 3 deletions

View File

@ -1,6 +1,6 @@
# Supported tags and respective `Dockerfile` links
- [`latest`, `base` (*Dockerfile*)](https://github.com/clearlinux/docker-brew-clearlinux/blob/3c63fc062b28b544e605b08e49a120c655a3ef8d/Dockerfile)
- [`latest`, `base` (*Dockerfile*)](https://github.com/clearlinux/docker-brew-clearlinux/blob/d81cccb0d30f3191ddddc521b96b9c6445617c81/Dockerfile)
For more information about this image and its history, please see [the relevant manifest file (`library/clearlinux`)](https://github.com/docker-library/official-images/blob/master/library/clearlinux). 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%2Fclearlinux).

View File

@ -28,10 +28,12 @@
- [`4.6.1.3-onbuild` (*4.6.1.3/onbuild/Dockerfile*)](https://github.com/mono/docker/blob/f0f1e0b9f693bd7c58d9623d402c8dc69234bbe1/4.6.1.3/onbuild/Dockerfile)
- [`4.6.1.5`, `4.6.1` (*4.6.1.5/Dockerfile*)](https://github.com/mono/docker/blob/8e5f8d9d00f596b838bf8d7d307ddb47f008a691/4.6.1.5/Dockerfile)
- [`4.6.1.5-onbuild`, `4.6.1-onbuild` (*4.6.1.5/onbuild/Dockerfile*)](https://github.com/mono/docker/blob/8e5f8d9d00f596b838bf8d7d307ddb47f008a691/4.6.1.5/onbuild/Dockerfile)
- [`4.6.2.16`, `4.6.2`, `4.6`, `4`, `latest` (*4.6.2.16/Dockerfile*)](https://github.com/mono/docker/blob/1db7e68061e2aaf81ed5ac413c217a7fd12c0228/4.6.2.16/Dockerfile)
- [`4.6.2.16-onbuild`, `4.6.2-onbuild`, `4.6-onbuild`, `4-onbuild`, `onbuild` (*4.6.2.16/onbuild/Dockerfile*)](https://github.com/mono/docker/blob/e1b6667f66443a0b768d9681c68bbb1e2f898601/4.6.2.16/onbuild/Dockerfile)
- [`4.6.2.16`, `4.6.2`, `4.6` (*4.6.2.16/Dockerfile*)](https://github.com/mono/docker/blob/1db7e68061e2aaf81ed5ac413c217a7fd12c0228/4.6.2.16/Dockerfile)
- [`4.6.2.16-onbuild`, `4.6.2-onbuild`, `4.6-onbuild` (*4.6.2.16/onbuild/Dockerfile*)](https://github.com/mono/docker/blob/e1b6667f66443a0b768d9681c68bbb1e2f898601/4.6.2.16/onbuild/Dockerfile)
- [`4.6.2.7` (*4.6.2.7/Dockerfile*)](https://github.com/mono/docker/blob/f370f5daa6344f6006f40e9cb638aef38faa67a0/4.6.2.7/Dockerfile)
- [`4.6.2.7-onbuild` (*4.6.2.7/onbuild/Dockerfile*)](https://github.com/mono/docker/blob/a41b568af8e26dac60a11432b5bb1c910d44f44a/4.6.2.7/onbuild/Dockerfile)
- [`4.8.0.495`, `4.8.0`, `4.8`, `4`, `latest` (*4.8.0.495/Dockerfile*)](https://github.com/mono/docker/blob/0dcec42351bdb86248361a5eff6cafbc99a538ce/4.8.0.495/Dockerfile)
- [`4.8.0.495-onbuild`, `4.8.0-onbuild`, `4.8-onbuild`, `4-onbuild`, `onbuild` (*4.8.0.495/onbuild/Dockerfile*)](https://github.com/mono/docker/blob/0dcec42351bdb86248361a5eff6cafbc99a538ce/4.8.0.495/onbuild/Dockerfile)
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).

View File

@ -143,6 +143,8 @@ EOSQL
These initialization files will be executed in sorted name order as defined by the current locale, which defaults to `en_US.utf8`. Any `*.sql` files will be executed by `POSTGRES_USER`, which defaults to the `postgres` superuser. It is recommended that any `psql` commands that are run inside of a `*.sh` script be executed as `POSTGRES_USER` by using the `--username "$POSTGRES_USER"` flag. This user will be able to connect without a password due to the presence of `trust` authentication for Unix socket connections made inside the container.
Additionally, as of [docker-library/postgres#253](https://github.com/docker-library/postgres/pull/253), these initialization scripts are run as the `postgres` user (or as the "semi-arbitrary user" specified with the `--user` flag to `docker run`; see the section titled "Arbitrary `--user` Notes" for more details).
You can also extend the image with a simple `Dockerfile` to set a different locale. The following example will set the default locale to `de_DE.utf8`:
```dockerfile

76
znc/README.md Normal file
View File

@ -0,0 +1,76 @@
# Supported tags and respective `Dockerfile` links
- [`1.6.4`, `1.6`, `latest` (*full/Dockerfile*)](https://github.com/znc/znc-docker/blob/7bf73d259149c476f09d765a008973076d0e48cb/full/Dockerfile)
- [`1.6.4-slim`, `1.6-slim`, `slim` (*slim/Dockerfile*)](https://github.com/znc/znc-docker/blob/7bf73d259149c476f09d765a008973076d0e48cb/slim/Dockerfile)
For more information about this image and its history, please see [the relevant manifest file (`library/znc`)](https://github.com/docker-library/official-images/blob/master/library/znc). 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%2Fznc).
For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see [the `repos/znc/tag-details.md` file](https://github.com/docker-library/repo-info/blob/master/repos/znc/tag-details.md) in [the `docker-library/repo-info` GitHub repo](https://github.com/docker-library/repo-info).
# What is ZNC?
ZNC is an IRC network bouncer (BNC). It can detach the client from the actual IRC server, and also from selected channels. Multiple clients from different locations can connect to a single ZNC account simultaneously and therefore appear under the same nickname on IRC.
[ZNC Wiki](http://znc.in/)
# How to use this image
ZNC in this image stores its configuration in `/znc-data`. If you have existing configuration, you can reuse it with `-v $HOME/.znc:/znc-data`. Alternatively, you can create a new config in a volume or in a local dir. The examples below assumes a volume named `znc-cfg`.
```console
$ docker run -it -v znc-cfg:/znc-data znc --makeconf
```
To run ZNC:
```console
$ docker run -p 6697:6697 -v znc-cfg:/znc-data znc
```
The port should match the port you used during `--makeconf`. Note that 6667 is often blocked by web browsers, and therefore is not recommended.
If you use any external module, put the .cpp, .py or .pm file to `/znc-data/modules` (you may need to create that directory).
Musl silently doesn't support `AI_ADDRCONFIG` yet, and ZNC doesn't support [Happy Eyeballs](https://en.wikipedia.org/wiki/Happy_Eyeballs) yet. Together they cause very slow connection. So for now IPv6 is disabled here.
# Image Variants
The `znc` images come in many flavors, each designed for a specific use case.
## `znc:<version>`
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
## `znc:slim`
This image is smaller, but it doesn't support external modules. If you need any external C++, Perl or Python module, use `latest` instead of `slim`.
# License
View [license](https://github.com/znc/znc/blob/master/LICENSE) [information](https://github.com/znc/znc/blob/master/NOTICE) for the software contained in this image.
# Supported Docker versions
This image is officially supported on Docker version 1.13.1.
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
## Issues
If you have any problems with or questions about this image, please contact us through a [GitHub issue](https://github.com/znc/znc-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/znc/znc-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.
## Documentation
Documentation for this image is stored in the [`znc/` directory](https://github.com/docker-library/docs/tree/master/znc) 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.