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

Documentation Bug

This concerns 1.x (1.7 specifically being used here) but may also apply to 2.x, and concerns the documentation more than the software.

What did you do?

We added our AWS VPC CIDR to our whitelisting.

What did you expect to see?

Especially helpful if you're in the profile view in the single-column-layout. Apparently the top bar only reacts to the back button which is rather inconvenient.

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

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

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):

Currently when adding an item to your cart, it only updates the cart counter graphic for that browser instance, not all connected clients. Using SignalR it should be relatively straightforward to update the cart counter on all connected clients.

The problem as far as I understand is that libfoo.so's only knowledge about libcuda.so is its SONAME, which is libcuda.so.1, so a binary wanting to link in libfoo.so needs to know who to find libcuda.so.1 in order to verify the available symbols. Generally, ld's suggestion is to use -rpath-link to provide the path to the library, but the nvidia docker repository doesn't come with the symlink to li

This issue is to support the following netdevice ioctls.
SIOCGIFMAP
SIOCGIFTXQLEN
SIOCGIFDSTADDR
SIOCGIFBRDADDR

The steps to get the laravel-horizon container up and running properly are very confusing, and not "officially" documented anywhere.

I've followed this and this, and while it appears to finally be working now, I don't know which of the steps I followed were actually necessary, and which may just

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