604f8889f5
/etc/apache2/apache2.conf was configured to log in this way: > ErrorLog /proc/self/fd/2 > CustomLog /proc/self/fd/1 combined This causes apache to reopen the already-opened fds. It works fine when the file descriptors are pipes or ttys but it fails when they are Unix sockets because sockets cannot be opened with the open() syscall. The issue happens when apache is connected to systemd-journald, like in the rkt container run-time. This patch uses "cat" to directly write to the stdio fds without reopening them. apache2.conf now looks like: > ErrorLog "|$/bin/cat 1>&2" > CustomLog "|/bin/cat" combined It works both with Docker and rkt (tested with and without --interactive). Symptoms: > [ 2673.478868] apache2-foreground[4]: (6)No such device or address: > AH00091: apache2: could not open error log file /proc/self/fd/2. See also: https://github.com/coreos/rkt/issues/2300 |
||
|---|---|---|
| apiserver | ||
| aws_ebs | ||
| azure_file | ||
| blog-logging | ||
| cassandra | ||
| celery-rabbitmq | ||
| cephfs | ||
| cluster-dns | ||
| elasticsearch | ||
| experimental/persistent-volume-provisioning | ||
| explorer | ||
| fibre_channel | ||
| flexvolume | ||
| flocker | ||
| glusterfs | ||
| guestbook | ||
| guestbook-go | ||
| hazelcast | ||
| https-nginx | ||
| iscsi | ||
| javaee | ||
| javaweb-tomcat-sidecar | ||
| job | ||
| k8petstore | ||
| kubectl-container | ||
| meteor | ||
| mysql-cinder-pd | ||
| mysql-galera | ||
| mysql-wordpress-pd | ||
| newrelic | ||
| nfs | ||
| nodesjs-mongodb | ||
| openshift-origin | ||
| phabricator | ||
| rbd | ||
| redis | ||
| rethinkdb | ||
| runtime-constraints | ||
| selenium | ||
| sharing-clusters | ||
| spark | ||
| storm | ||
| vitess | ||
| OWNERS | ||
| README.md | ||
| doc.go | ||
| examples_test.go | ||
| guidelines.md | ||
| pod | ||
| scheduler-policy-config-with-extender.json | ||
| scheduler-policy-config.json | ||
| simple-nginx.md | ||
README.md
PLEASE NOTE: This document applies to the HEAD of the source tree
If you are using a released version of Kubernetes, you should refer to the docs that go with that version.
The latest release of this document can be found [here](http://releases.k8s.io/release-1.2/examples/README.md).Documentation for other releases can be found at releases.k8s.io.
Kubernetes Examples: releases.k8s.io/HEAD
This directory contains a number of examples of how to run real applications with Kubernetes.
Demonstrations of how to use specific Kubernetes features can be found in our documents.
Maintained Examples
Maintained Examples are expected to be updated with every Kubernetes release, to use the latest and greatest features, current guidelines and best practices, and to refresh command syntax, output, changed prerequisites, as needed.
| Name | Description | Notable Features Used | Complexity Level | |
|---|---|---|---|---|
| Guestbook | PHP app with Redis | Replication Controller, Service | Beginner | |
| WordPress | WordPress with MySQL | Deployment, Persistent Volume with Claim | Beginner | |
| Cassandra | Cloud Native Cassandra | Daemon Set | Intermediate |
Note: Please add examples to the list above that are maintained.
See Example Guidelines for a description of what goes in this directory, and what examples should contain.