Move all Dockerfile samples to non-root user

Expected Behaviour

As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.

Current Behaviour

Installation method "Method

What is the problem?

I've succesfully installed Gitea using the one-click install on a fresh install of CapRover. When I try to install drone-gitea using the one-click Install, I get the following error at the 7th step: "Failed: Error: Request failed with status code 500" .

If applicable, content of captain-definition file:

N/A

Steps to reproduce the problem:

1. Install Gitea

The platform-info command only shows the list of build versions of each platform.

It was be great if the command also show information about the platform content, like supported versions, configuration files supported, etc..

One way to do this is creating a yaml file .spec inside each platform, with these informations.
ex:

name: python
default_version: "2.7.14"
supported_v

Expected Behavior

Documented install procedure at https://knative.dev/docs/serving/installing-cert-manager/ works fine.

Actual Behavior

~/knative-workspace/cert-manager-0.6.1$ kubectl apply -f deploy/manifests/cert-manager.yaml
unable to recognize "deploy/manifests/cert-manager.yaml": no matches for kind "Deployment" in version "apps/v1beta1"
unable to recognize "deploy/manifests

We're looking into using Empire to deploy our application, but the documentation didn't make it entirely clear to me how to go about setting up Empire for production. Is there a step-by-step guide/example anywhere?

General information

i am installing kubernetese in ubuntu 18.04. first i installed kubect, then virtual box than minikube. when i check the version of kubectl it gives the following error..

• Minishift version:
• OS: Linux / macOS / Windows
• Hypervisor: KVM / Hyper-V / VirtualBox / hyperkit

error: Missing or incomplete configuration info. Please point to an existing, complete

The problem faced currently?

docs specifies how to clear events_log table
by manually running queries

How can we solve it?

It would be better if user has a option in mission control to such as automatic cleaning
which will clean the failed records weekly or daily basis

If you want this feature to be implemented, give it a thumbs up reaction, so that we can determine which features a

We've tried for feature parity, but there are certain things that are still specific to one of the proxies. It would be helpful to have some sort of documentation tag for these features.

Describe the bug
I just signed up and went to the public templates section.
There is only one template shown (see screenshot).

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://cloud.lastbackend.com/templates#public'
2. See error

Expected behavior
I was expecting a lot more, e.g. Wordpress, MongoDB, Bootstrap, PostgreSQL, Etherpad, Apache, CouchDB, SearX, wall

deis logs -a <app_name> --lines -1 not spitting out all logs since app launch. As a workaround you have to supply an arbitrarily large number i.e - deis logs -a <app_name> --lines 10000.

I've been looking at the repo structure and would like to make the core repo more approachable. I've been procrastinating on finishing #91 due to travel, #142 will target the README and #152 is in, so here are a few ideas:

• Finish #91, agree on #142
• Keep only core docs (CONTRIBUTING.md, a single INSTALL.md) in the main repo
• Move detailed documentation to the website's repo (this is the

We have some services that need to be exposed to the public network, so a common load balancer is required to route.

Consider using ingress nginx for implementation

Redirect list:

sample host: opcloud.com
HTTP   www.opcloud.com => openpitrix-dashboard:8000
HTTP   api.opcloud.com => openpitrix-api-gateway:9100
WS  api.opcloud.com/io => 

We should check whether there is already some ingress and return an error, avoiding ingress duplication.

We should also change the HasIngress verification on the cloud providers, as they may be misleading (they are a test to see if ingress is implemented).

1、当没有API文档时的空数据提示
2、当没有搜索到API文档时的空数据提示

I'm getting this error if minikube is stopped on snow create. I see that there is a catch around this command. Don't know why this error is printed. The script continues execution.

Which cloud provider are you hosting with? (minikube,gcp,digitalocean) [m,g,d] m
Note: Minikube is for development purposes only.
minikube status
host: Stopped
kubelet:
apiserver:
kubectl:
Command fai