The publish filter looks to be filtering on the wrong values (and the TestPsListContainersFilterPorts is incorrect); see moby/moby#27557 (comment)

Create some containers;

docker run -d --name test_no_ports nginx:alpine
docker run -d --name test_port_1080 -p 1080:80 nginx:alpine
docker run -d --name test_port_1090 -p 1090:80 nginx:alpine

#6116 uses hardcoded maximum number of active processes (default actually).

it is configurable value, we could collect it and calculate system active processes usage % and warn user based on it.

some info from @apardyl

Yes, we can do that. We would probably also need to read /proc/sys/kernel/threads-max - pid_max is the max PID that can be assigned, threads-max is the actual limit of t

Do you want to request a feature or report a bug?

Can anyone please help me out. I'm getting error while generating KONG client credentials on HTTP port 8000.

{ "error_description": "You must use HTTPS", "error": "access_denied" }

I have added trusted_ips = 0.0.0.0/0,::/0 in kong.conf also, but it didn't work.

the SSE feed should cache repository permissions to reduce database lookups. There are no documented issues of this being a problem, but this sort of performance improvements seems like low hanging fruit.

Currently for example https://mastodon.social/api/v1/instance contains a lot of information like title which is used for example by https://the-federation.info/mastodon to show a display name for a Mastodon server. NodeInfo was introduced in Mastodon 3.0 but it doesn't contain a server display name.

Due to the way NodeInfo is designed, it doesn't have a display name field. By community conven

On https://docs.docker.com/compose/compose-file/#restart it says:

no is the default restart policy, and it does not restart a container under any circumstance. When always is specified, the container always restarts. The on-failure policy restarts a container if the exit code indicates an on-failure error.

After reading this I have no idea what "restart" does. I've seen a lot of times peop

When using AUFS as the storage driver in docker (or podman, etc.) then the maximum number of layers that can have data is "42".

This is because each layer that has data is unpacked into the file-system and then union mounted over each other. AUFS only allows a maximum of 42 layers to be mounted over each other.

The hard-limit is 127 data layers which is due to the maximum number of argu

as multi-stage builds is a thing now (and a useful thing) it is a good idea to provide a sample example (maybe just link)

https://docs.docker.com/engine/userguide/eng-image/multistage-build/

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

Overview of the feature request

Have a new needle in the server subgenerator for adding new log level configuration.

Motivation for or Use Case

hipster-labs/generator-jhipster-entity-audit#62 is a good example for the need.

Related issues or PR

Bug description
Don´t show table correctly

Expected behavior
A Table view normal

Steps to reproduce the issue:
Crreate a container with large ENV variable

Technical details:

• Portainer version: 1.21.0
• Docker version (managed by Portainer): 18.09.3
• Platform (windows/linux): linux
• Command used to start Portainer (docker run -p 9000:9000 portainer/portainer):

**What kind of request is this (question/bug/enhan

Is there a reference somewhere of how all of the components included hang together, how each of them is structured internally and how they communicate to each other - UML or any other sort of diagrammed/detailed description?

I have it deployed fine, it all works as far as that part goes, but it would be much easier to get into the detail by following some documentation than to figure it all o

The examples for vhost configs for server/location blocks on the README only provide settings, they don't seem to explain much about intended content/blocks.

• Are settings for server blocks only relevant?(LetsEncrypt companion seems to insert location blocks instead of using _location file)
• Adding location blocks in example.com_location would be nested blocks presumably or only for sett

When a container image tag is too long, it causes the fav and close icons to be shifted. Max width should be 120px - child span should be inline-block

I have a angular 4 project which i'm working from last 2 years and as I didn't had any new package to add, I didn't ran npm install for almost an year. Few days back I needed a package to install and hence did npm install defining it in package.json file, after which my AOT build started giving some problem. Then I changed my typescript package from ~2.2.2 to ~2.8.0 after that it worked but it's t

The steps for updating the repository keys for RHEL-based distributions in https://nvidia.github.io/nvidia-docker/ should read:

$ DIST=$(sed -n 's/releasever=//p' /etc/yum.conf)
$ DIST=${DIST:-$(. /etc/os-release; echo $VERSION_ID)}
$ sudo rpm -e gpg-pubkey-f796ecb0
$ sudo gpg --homedir /var/lib/yum/repos/$(uname -m)/$DIST/*/gpgdir --delete-key f796ecb0
$ sudo gpg --homedir /var/lib/

The accounts query includes the field shopId twice with different description:

https://github.com/reactioncommerce/reaction/blob/8ed0165a7ab2c07ddfa394317d12c34ca57c37ee/src/core-services/account/schemas/account.graphql#L444
https://github.com/reactioncommerce/reaction/blob/8ed0165a7ab2c07ddfa394317d12c34ca57c37ee/src/core-services/account/schemas/account.graphql#L447

Versions

la

Hi, I'm Yevgeny Pats Founder of Fuzzit - Continuous fuzzing as a service platform.

We have a free plan for OSS and I would be happy to contribute a PR if that's interesting.
The PR will include the following

• go-fuzz fuzzers (This is generic step not-connected to fuzzit)
• Continuous Fuzzing of master branch which will generate new

The log view currently serves to only tail a containers logs (including last 10 by default).

This issue tracks the implementation of a more fully featured container log pager (navigation, search, etc.)

in
If you want to use TLS using your own certificates, set tls-listener to :443, force-https, tls-cert=file and tls-private-key.

replace tls-cert=file with tls-cert-file

Expected behavior

Sample app deployed to GKE cluster

Actual behavior

1.FATA[0011] reading manifests: kubectl create: Running [kubectl --context create --dry-run -oyaml -f k8s-pod.yaml]: stdout , stderr: Unable to connect to the server: net/ht

Info:

• Docker version ($ docker --version): version 18.09.7, build 2d0083d
• Laradock commit ($ git rev-parse HEAD): 11c59aebe7d5b316f5c5b8fdfe38849d2b248700
• System info (Mac, PC, Linux): Linux
• System info disto/version: 18.04.1-Ubuntu

Issue:

I followed steps mentioned here https://laradock.io/documentation/#install-supervisor to install supervisor inside workspace service