Is your feature request related to a problem? Please describe.
The drop down list for adding/editing volumes on the add/edit container page doesn't have a logical order.

Describe the solution you'd like
A simple alphabetical order would make things easier.

Info:

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

Issue:

The /opt/mssql/bin/mssql-conf set-sa-password script does not work at all.
Not only that

The README has relative links to other Markdown files that only work in GitHub and not in the Docker Hub.

The document sad that watchtower has a cron like --schedule parameter, but there was not much information how to use it.

• Why there are 6 Parameters, what is the sixed about (seconds i guess!?), and is it at the beginning or the end?
• The example is nearly useless, without saying what time/date/intervall it will trigger the update
• Some more info what crontab syntax are supported e.g. slas

This is a...

• Request for a new or modified feature
• Issue trying to run the docker image
• Issue trying to build / test / de

I just noticed the readme at https://hub.docker.com/r/tiangolo/uwsgi-nginx-flask/ is cut off at the end, and I thought it was a mistake until I realized that the readme on Github is not truncated, so I assume Docker Hub just has a maximum length. I think it would be helpful to have a note at the end of the readme on Docker Hub saying to check the Github repo to continue reading. I wouldn't have re

The documentation doesn't mention anything about Swarm, but there are configurations relevant to it:

I think SWARM=true needs to be passed.
It seems that then LABEL_ENABLE defaults to true, so MONITOR is ignored. I haven't tried setting it to false.

Hi, can you write small example, how to use this image in docker-compose.yml?

We need a proper website, with docs, examples, etc.
Basic static generation (e.g. with Gatsby) from markdown (to allow for current docs reuse) would probably work just fine.

https://goreleaser.com may be better than the crap I threw together.

We should add a CLI argument to add extra lines of configuration when the bootstrap configuration is applied to the device.

vrnetlab has no aspiration of becoming a generic configuration management system. The focus has always been, and will continue to be, on doing the minimal amount of configuration so that the router can then be configured through NETCONF/YANG. vrnetlab configures this boots

The openj9 jdk14 release file names were incorrect because changes needed to be made to various build scripts to change the download file name prefix from OpenJDK14 to OpenJDK14U.

This requirement is not mentioned in the RELEASING.md file.

The document should include details of which build scripts to be changed for the release engineer to either implement or check.

Sorry to open an issue on this but I have been racking my brain and googling and can't figure out what I need to change to get the consul service working.

The documentation states: "This container has been setup to automatically connect to a Consul cluster, created with a service name of consul."

I'm trying to bring this up in a standalone vagrant vm:

docker run -d --name consul-test smeb

I'm new to Docker, so forgive my ignorance, but I'm struggling to understand what these directions are telling me to do:

https://github.com/whisklabs/docker-it-scala#configuration

According to this whisklabs/docker-it-scala#7 you simply need to set that environment variable for DOCKER_HOST and all unit tests should then run just fine, but on a fresh install of Doc

@yegor256 and @alex-palevsky, the information on how to build/run tests of rultor locally (for example, mentioned here) seems to be missing from README.md or any other document in the repository.

Also note the CONTRIBUTING.md file was deleted in commit https:

I am receiving the following error when attempting to spin up jupyterhub.

Error

jupyterhub-db | FATAL:  password authentication failed for user "postgres"

Command Ran

docker-compose up

Troubleshooting Completed

1. Confirmed secrets/postgres.env exists and has environment variable POSTGRES_PASSWORD set to some large hex.
2. Confirmed docker-compose file

e.g. if running with runlike -i ... then make the command output -i, even if inspected container runs in daemon mode
relevant for -i, -d, -t... and probably several other options.