Saravanan666/pypi-org huggingface dataset:
Package: docker-tasks
docker-tasksdocker-tasksis a tool for executing periodic tasks via docker exec.
It is looking up for running docker images and execute the specified commands in the matching containerAn use case could be to dump allPostgreSQLbased images to the container related volume.
This allow me to backup/var/lib/docker/volumes/with apg_dumpgenerated database dump inside my volumes.Installationpip install docker-tasksCreate adocker-tasks.ymlwith example commandsimages:
    ubuntu:
      '*':
        - ps aux

    postgres:
      '9.*':
        - /bin/sh -c "pg_dump -U postgres postgres > /var/lib/postgresql/data/db_backup_$(date +%u).sql"Usageusage: docker-tasks [-h] [-c CONFIG] [-v]

optional arguments:
  -h, --help            show this help message and exit
  -c CONFIG, --config CONFIG
                        Config yaml. Default (docker-tasks.yml)
  -v, --verbose         Increase output verbosity
Package: docker-tidy
docker-tidyKeep docker hosts tidyThis project is a fork ofYelp/docker-custodian. Keep docker hosts tidy.You can find the full documentation athttps://docker-tidy.geekdocs.de.ContributorsSpecial thanks to allcontributors. If you would like to contribute,
please see theinstructions.LicenseThis project is licensed under the Apache-2.0 License - see theLICENSEfile for details.
Package: docker-travis-php
Shits out a simple dockerfile for php projects based upon a .travis.ymlLiterally don’t use this and assume it’ll work. It probably won’t. Hence the description.Literally the worst. I can’t even.InstallationUsing PIP via PyPI:pip install docker-travis-phpUsing PIP via Github:pip install git+git://github.com/josegonzalez/docker-travis-php.git#egg=docker-travis-phpUsageIn a directory with a.travis.yml, run the following:docker-travis-phpYou will now have aDockerfilein that directory that can be run via the following command:# builds the ``before_script`` and ``script`` sections
# useful for "local" travis runsdockerbuild.The default debian packages that are installed (before php extensions) are as follows:git-corelibcurl4-openssl-devlibicu-devphp-pearphp5-cliYou can add more by using the following environment variable:exportPACKAGES=wgetdocker-travis-phpBy default, the following extensions are built:curlintlmbstringmysqlredisxdebugYou can configure this using the following environment variable:exportEXTENSIONS=curl,intl,mbstringdocker-travis-php
Package: docker-tunnel
docker-tunnelis a console utility to use remote docker with SSH tunnel.If you are using OS X or a Linux distribution with docker-unsupported kernel,
no more running a virtual machine or ssh to a remote shell.InstallationWith pip:$ pip install docker-tunnelWithpipsi(Recommended):$ pipsi install docker-tunnelUsage$ docker-tunnel user@example.com
(user@example.com) $
(user@example.com) $ echo $DOCKER_HOST
127.0.0.1:4243
(user@example.com) $ docker ps  # go ahead
...
(user@example.com) $ ^D  # ctrl-d
$More options:$ docker-tunnel --helpShell Theme IntegrationInside the tunnel injected shell, the environment variableDOCKER_HOSTandDOCKER_PROMPT_INFOwill be assigned. They can be used in your shell theme to prompt you which tunnel is using.There is an example,my custom themefor OH-MY-ZSH.TroubleshootingError response from daemon: client and server don't have same version (client : 1.14, server: 1.12)The docker in source of CentOS 7 is using API 1.12 but the docker client in Homebrew of OS X is not. You can downgrade the docker client with Homebrew:$ brew versions docker
...
1.0.0    git checkout c513c42 /usr/local/Library/Formula/docker.rb
...
$ cd /usr/local/Library/Formula  # now we install the old version of docker
$ git checkout c513c42 -- docker.rb
$ brew unlink docker
$ brew install docker
$ git checkout HEAD -- docker.rb
$ cd -
$ brew info docker  # check the installed versions and current version
...
/usr/local/Cellar/docker/1.1.1 (9 files, 9.8M) *
  Poured from bottle
/usr/local/Cellar/docker/1.2.0 (9 files, 6.6M)
  Poured from bottle
...
$ docker-tunnel user@example.com
(user@example.com) $ docker version
Client version: 1.0.0
Client API version: 1.12
...
(user@example.com) $ exit
$ brew switch 1.2.0  # restore to latestbind: Address already in use. cannot listen to port: 4243You can find out the process which held the4243port withsudo lsof-i:4243and decide to kill it or pick another port with--local-port.channel 1: open failed: connect failed: Connection refused. 2014/09/06 13:08:57 Gethttp://127.0.0.1:4243/v1.14/info:EOFDoes the docker server listen on127.0.0.1:2375? You may have to set correct server info with--remote-hostand--remote-port.Known BugsThe ssh tunnel can be authenticated with public key only. The password prompt will caused a crash.IssuesIf you want to report bugs or request features, please create issues onGitHub Issues.
Package: docker-tutorial
Docker Tutorial===============The Docker tutorial is an interactive learning environment to get familiar with the Docker commandline.Simple Usage------------Generally this application is used in the www.docker.io website. It's source can be found onhttps://github.com/dotcloud/www.docker.io/. By installing that you will get this app 'for free' as adependency.However, this app is made to also be usable inside other Django applications. All that is required is toadd git+https://github.com/dhrp/docker-tutorial.git#egg=DockerTutorial-dev to your requirements.txtand it will be installed by pip upon pip install -r requirements.txtTo include it* Make sure your "host" app uses the same python environment* In your "host" app settings include "docker_tutorial"* in a template {% include 'tutorial/snippet.html' %}* in your urls.py add url(r'^tutorial/', include('docker_tutorial.urls')),* in your settings make sure you include the session middleware:When you want to make changes-----------------------------* First create or switch to a virtual environment in which you have the "host" app into which you wouldlike to embed the tutorial. e.g. a clone of the the Docker website (before you ran install)* Clone this repository:git clone https://github.com/dhrp/docker-tutorial.git* Switch to the dir:cd docker-tutorial* Install the application with the -e (editable) flag.pip install -e .This will setup the symlinks such that you don't need to run setup.py every time you want to see achange. i.e. your local repository is now linked into the environment.Running the unit tests----------------------* ./runtests.pyRunning code coverage---------------------* coverage run ./runtests.py && coverage html --include="./docker_tutorial/*"Happy coding!
Package: docker-upload-and-build
Installation$[sudo]pipinstalldocker-upload-and-build$[sudo]npmi-gdocker-upload-and-buildProsupload sources to server and build docker imageno need docker hub and docker desktopFeatures.dockerignoreas rsyncexclude-fromfile (optional)Examplesdocker-upload-and-builduser@hostnametag.readme42.com
Package: docker-volume-manager
# docker-volume-managerManage your named docker volumes using this simple script.### Managing docker-volumes with a simple script.-----### Usage:1. Clone this repository:`git clone https://github.com/ansrivas/docker-volume-manager.git`2. Go to the directory and install this locally:`cd docker-volume-manager && pip install -e .`3. To save a named-docker-volume:`docker-volume-manager save --volume <existing_named_volume>`4. To load an already saved local volume to a named-docker-volume:`docker-volume-manager load --volume <new_volume_name> --path <absolute_path_to_your_saved_volume>`5. More options can be seen by using the help:`docker-volume-manager --help`6. A simple use case could be to backup files:```bash# cat backup_script.pyimport osimport subprocessimport timefiles = os.listdir('./')tars = [f for f in files if f.endswith('.tar.gz')]to_keep = sorted(tars)[-7:]for tar in tars:if tar not in to_keep:os.remove(tar)command = ["/usr/bin/docker-volume-manager", "save", "--volume", "your_docker_data_volume", "--interactive","False"]subprocess.check_output(command )```###### Disclaimer: Do not use it directly in a production environment. Test it locally before using it out there.
Package: dockerwatch
Monitoring script for Docker.Supported Metrics:Number of containersSupported Backends:CloudWatchInstallation$ pip install dockerwatchUsage$ dockerwatch --settings=/path/to/dockerwatch.jsondockerwatch.json{"DOCKER_API_VERSION":"1.30","AWS_REGION_NAME":"...","AWS_ACCESS_KEY_ID":"...","AWS_SECRET_ACCESS_KEY":"...","AWS_ASG_NAME":"..."}
Package: docker-windows-volume-watcher
This script monitors directory bindings of Docker containers on Windows hosts and notifies containers about file changes.The script aims to be workaround for the problem of file change events propagation on Windows hosts. Due to limitations of CIFS implementation in Linux kernel, file change events in mounted folders of host are not propagated to container by Docker for Windows. This problem renders watch mode of modern frameworks (e.g. Jekyll, ng-cli, etc.) development servers useless, since containers are not notified about file changes. This problem is described onDocker Community Forums.InstallationThis script can be installed with pip (both Python 2 & 3 are supported).pip install docker-windows-volume-watcherUsageMonitor all directory bindings of all containers. The script will listen for container start/stop events and notify all running containers about file changes.docker-volume-watcherMonitor only bindings of containercontainer_name.docker-volume-watcher container_nameMonitor only binding ofcontainer_nameto host directoryC:\some\directory.docker-volume-watcher container_name C:\some\directoryYou can also specify wildcards with*and?characters. For example: monitor only bindings of containers with names containingmyprojectto directories starting withC:\project\folder\.docker-volume-watcher *myproject* C:\project\folder\*Do not monitor files/directories matching*.git*and*build*patterns:docker-volume-watcher -e"*.git*""*build*"If you experience duplicate notification issue (e.g.Duplicate notification - a single change triggers 2 notifications to the container), try event debounce feature:docker-volume-watcher --debounce 0.1Use flag-vto enable verbose output: the script will report start/stop events of eligible containers and print all detected file changes.LimitationsThe script doesn’t propagate to container file deletion events.The script requiresstatandchmodutils to be installed in container (this should be true by default for the most of containers).Implementation detailsThe script useswatchdogpackage to observe file change events of the host directory. Once file change event is fired the script reads file permissions of changed file (usingstatutil) and rewrites file permissions with the same value (usingchmodutil) thus triggering inotify event inside container.“Rewrite file permissions approach” was used instead of updating file last modified time withtouchutil. Since touching will cause event loop: touch will trigger file change event in Windows, script will handle this event and touch file again, etc.
Package: docker-with-criu
Docker SDK for PythonA Python library for the Docker Engine API. It lets you do anything thedockercommand does, but from within Python apps – run containers, manage containers, manage Swarms, etc.InstallationThe latest stable versionis available on PyPI. Either adddockerto yourrequirements.txtfile or install with pip:pip install dockerOlder versions (< 6.0) required installingdocker[tls]for SSL/TLS support.This is no longer necessary and is a no-op, but is supported for backwards compatibility.UsageConnect to Docker using the default socket or the configuration in your environment:importdockerclient=docker.from_env()You can run containers:>>>client.containers.run("ubuntu:latest","echo hello world")'hello world\n'You can run containers in the background:>>>client.containers.run("bfirsh/reticulate-splines",detach=True)<Container'45e6d2de7c54'>You can manage containers:>>>client.containers.list()[<Container'45e6d2de7c54'>,<Container'db18e4f20eaa'>,...]>>>container=client.containers.get('45e6d2de7c54')>>>container.attrs['Config']['Image']"bfirsh/reticulate-splines">>>container.logs()"Reticulating spline 1...\n">>>container.stop()You can stream logs:>>>forlineincontainer.logs(stream=True):...print(line.strip())Reticulatingspline2...Reticulatingspline3......You can manage images:>>>client.images.pull('nginx')<Image'nginx'>>>>client.images.list()[<Image'ubuntu'>,<Image'nginx'>,...]Read the full documentationto see everything you can do.
Package: dockerwithgitlabsecrets
Docker With GitLab SecretsWraps Docker to run with GitLab build variables.InstallationPrerequisites: - Python >= 3.6 - dockerStable releases can be installed viaPyPI:$pipinstalldockerwithgitlabsecretsBleeding edge versions can be installed directly from GitHub:$pipinstallgit+https://github.com/wtsi-hgi/docker-with-gitlab-secrets.git@commit_id_or_branch_or_tag#egg=dockerwithgitlabsecretsUsageWrap your prefixed Docker command with:usage:docker-with-gitlab-secrets[-h][--dwgs-configDWGS_CONFIG][--dwgs-projectDWGS_PROJECT][--env-fileENV_FILE]DockerWithGitLabSecretsoptionalarguments:-h,--helpshowthishelpmessageandexit--dwgs-configDWGS_CONFIGlocationoftheconfigurationfile(willdefaultto/Users/cn13/.dwgs-config.yml)--dwgs-projectDWGS_PROJECTGitLabproject(ifnotnamespacedintheform"namespace/project",thedefaultnamespacedefinedintheconfigurationfilewillbeused).Ifnotdefined,thedefaultprojectintheconfigurationfilewillbeusedExamplesRun a new container with secrets from a GitLab project:docker-with-gitlab-secrets--dwgs-configmy-config.yml--dwgs-projectmy-project\run--rmalpineprintenvGITLAB_SECRETWrapping unrelated Docker commands will still work:docker-with-gitlab-secrets--dwgs-configmy-config.yml\versionRun a container interactively that will have secrets from a GitLab
project in the environment:docker-with-gitlab-secrets--dwgs-configmy-config.yml--dwgs-projectmy-project\run--rm-itubuntuConfigurationExample:gitlab:
  url: https://gitlab.example.com
  token: my-token
  project: hgi-systems  # Optional default project, which will be overriden by if `dwgs-project` is specified
  namespace: hgi        # Optional default namespaceKnown IssuesDockercannot pass newlines in variables via
`–env-file`` <https://github.com/moby/moby/issues/12997>`__.
Therefore multiline GitLab variables with have their line-breaks
escaped to \n.
Package: docker-wrap
Docker-WrapA drop-in wrapper fordocker-composethat runs pre/post up and pre/post build scripts.I frequently have scripts I want to run before/afterdocker-composebuild/up.  This wrapper creates a standard way to run everything by
just wrappingdocker-composeand passing through all arguments.  You
use it wherever you normally usedocker-compose.  You could even
symlink it as docker-compose in your /usr/local/bin.The wrapper is smart enough to run your pre-build, even when build is
triggered by anupcommand.The pre-build script runs beforeDockerfileis loaded, so you cangenerateyourDockerfilefrom your pre-build script.If you're just pulling an image and not building a new image, the
pre/post build script does not run.InstallIf you want to install system-wide but also have edits you make here reflected in that system-wide install:python3 -m setup developOr just install it like you normally would:python3 -m setup installEventually, this will work, but I haven't uploaded it to PyPi yet:pip3 install docker-wrapUseFor any service, add an associative arrayx-wrapwith one or more
keys whose values are associative arrays namedbuildoruse.
Those associative arrays should containpreorpostkeys whose
values are paths to scripts to run.  See the example below.docker-wrapwill run anyprescript before it runs your command,
then run anypostscript.  A future feature will that be if aprescript prints a valid yaml structure,docker-wrapwill use that
script as thedocker-compose.ymlfor running the command.docker-wrappasses all arguments on todocker-compose.Something like this would work:docker-wrap up fooSample docker-compose.ymlversion: "3.9"
services:
  foo:
    x-wrap:
        build:
          pre: pre-build.sh bar baz
    build: barThe default directory for runningpre-build.shwill be thefoodirectory.  If you set context, it will be the context.Features Roadmap[X] Pre/post build scripts
[X] Allow pre script to replace Dockerfile
[ ] Allow pre script to replace docker-compose
[X] Pre/post up scripts
[ ] Use wrap instead of x-wrap
[ ] pip installableContributingActivity is in theGitHub
Repoand you can always
pop in tochat.opentechstrategies.comas well.Please run thepython qa
scripton the code
before submitting a PR.  That script just runs black, isort, mypy, and
tests (tho we have no tests yet).License and CopyrightCopyright 2020 James Vasile, published under the terms of AGPLv3 or
later.
Package: dockery
dockeryGraphical interface for Docker in your consoleInstallationFrom pippipinstall-UdockeryFrom sourcegitclonehttps://github.com/marianocarrazana/dockery.gitcddockery
pipinstall-e.# update only:gitpullUsageRun on your console:dockeryWarning:you will probably need to install and run dockery as a root user, or you can add permissions to your user to run docker followingthis instructions.Utilsdockerydf
dockeryps
dockeryvolumes
dockeryimages
dockerynetworks
dockerystats# Docker swarmdockeryconfigs
dockerysecretsYou specify the format output of these commands with the parameter--format, e.g:dockerydf--formatjson
dockerydf--formatyamlGet logsYou can useΞLogsbutton on the containers tabs to see the logs.Or you can use the logs command to visualize them:dockerylogs{container_name}You can use the parameter--streamto get the logs in real time, e.g:dockery logs {container_name} --streamEnjoy it!
Package: docker-zabbix-sender
RationaleDocker Zabbix Sender delivers a daemon script that push to Zabbix statistics about Docker containers.It leverages 2 interesting components:Zabbix maintains a tool titledzabbix-sender.
It is meant to pushZabbix trapper itemsefficiently.Docker 1.5.0 comes with Docker Remote API version 17, providing a newstats endpoint.
It allows the client to subscribe to a live feed delivering a container statistics.The daemon script stands in the middle of those 2 components.
It collects Docker containers statistics and transforms them in Zabbix trapper events.Published metricsThe daemon script already emits a collection of metrics: CPU, memory, and network usage.
The module’s API provide mechanism to easily extend the list of published events.DocumentationThe stable documentation is available onReadTheDocs
Package: dockflow
Dockflow CLIThis package requires docker to be installed and running on your machine.Getting startedInstall dockflow:pip install dockflowAuthenticate docker to pull from private GCR repository:2.1. First make sure that yourgcloudis authenticated.2.2. Ensure you are in the correct project usinggcloud config set project <project name>2.3. Usegcloud auth configure-dockerto auth docker to pull from private container repo.QuickstartEnsure that your docker file sharing settings allows access to your development directory.Navigate to the root directory of yourdagsfolder.Usedockflow configand enter your container repo url excluding the version.This will save the url in a config file.Eg.eu.gcr.io/<project>/<container>This should only be used if the container repo changes.If the image version tag is notcomposer-1.11.2-airflow-1.10.9specify the tag usingdockflow start -iv <version>Usedockflow start(This will mount the dag folder and start Airflow).Use the UI to add connections.Admin -> Connections -> CreateUsedockflow refreshto refresh the configs cache or to bundle configs.Remember to usedockflow stopto shut down the instance to save local machine resources.The state will be persisted in the same directory as thedagsfolder.To stop and remove the container usedockflow stop --rmAvailable composer versionscomposer-1.11.2-airflow-1.10.9 (default)composer-1.10.6-airflow-1.10.6 (No longer being updated)CloudSQL Proxydocker run -d \
  -v <PATH_TO_KEY_FILE>:/config \
  -p 127.0.0.1:5432:5432 \
  --network='dockflow' \
  --name='cloudsql' \
  gcr.io/cloudsql-docker/gce-proxy:1.17 /cloud_sql_proxy \
  -instances=<INSTANCE_CONNECTION_NAME>=tcp:0.0.0.0:5432 -credential_file=/config
Package: dockingFormatter
dockingFormatterSimple formatter for docking of the compound logs. That takes docking log and returns interesting findings in format of xlsx file.InstallationYou can install thedockingFormatterfromPyPI:pip install dockingFormatterorpip3 install dockingFormatterThe formatter is supported on Python3 and should be working fine on Python2.What it doesThe dockingFormatter is a simple command line application, it takes docking log and then finds lowest affinity for the given compound. Afterwards returns the inforamtion in form of xmls file looking like that:How to use$ dockingFormatter [DOCKING LOG FILE NAME]or with custom output file name$ dockingFormatter [DOCKING LOG FILE NAME] --outputfile [CUSTOM NAME with or without xmls extension on the end]to see all options and description you can use$ dockingFormatter --helpDeveloping dockingFormatterTo install dockingFormatter, along with the tools you need to develop and run tests, run the following in your virtualenv:$pipinstall-e.[dev]
Package: docking-py
Docking PythonDocking_py is a python library allowing a simplified use of the Smina, vina, qvina2 and qvinaw docking software. Docking_py can be easily automatize and scripted.Free software: GNU General Public License v2 (GPLv2)Documentation:https://docking-py.readthedocs.io.FeaturesPrepare receptors and ligands.Launch docking using:Autodock with or withoutGPUaccelerationVinaSminaQvina2QvinawCreditsThis package was created withCookiecutterand theaudreyr/cookiecutter-pypackageproject template.History0.1.0 (2020-04-15)First release on PyPI.
Package: dockit
Dockit- What is this?dockerTo launch, close and execute container with docker-compose and its relative services without change the directory.gitFuzzy the current location to pull all the submodules and specify the project if required.- History#dateversion12020/01/24v0.1.222020/01/27v0.1.432020/02/02v0.1.542020/02/13v0.1.652020/03/22v0.1.8v0.1.2Fixed dockit -u & -d cannot work properly when the project not located at $HOME directory.v0.1.4Replaced whole color module.v0.1.5Fixed display bug while remote added new branches.Removed optional argument-n, use positional argument instead.(default:basename of $pwd)v0.1.6Support pull a project and the all the submodules which belongs to the project without change the directory.Support change source directory by setting a environment variableexport DOCKIT_ROOT='~/your/custom/path'.v0.1.8Removed -l flag of _exec_container to solve some container cannot call go properly- How to installInstallpipinstalldockitSetup source root(Optional)
Make it temporary or add the following line to your.bashrc,.zshrcor profile to keep it permanently.exportDOCKIT_ROOT='~/TO/YOUR/CUSTOM/PATH'- How to usedockit.py[-h][-a][-p][-l][-c][-u][-d][-e][-s][project]-h, --helpshow this help message and exit-p, --git-pullpull git repository and all sub repositories-l, --docker-launch-serviceparse project prefix and launch ${PREFIX}_service-u, --docker-up-servicedocker-compose up -d container with the same name as project-a, --docker-attach-containerto keep attaching mode after docker-compose upped-d, --docker-down-servicedocker-compose down container with the same name as project-c, --docker-close-serviceparse project prefix and close ${PREFIX}_service-e, --docker-exec-containerdocker exec -it container bash-s, --docker-show-containersshow docker processes# .bashrc or .zshrcaliasgitpull="dockit -p"aliasrun="dockit -e"aliasup="dockit -u"aliasuu="dockit -l"aliasuuu="dockit -lu"aliasuur="dockit -lue"aliasuura="dockit -luea"aliasdown="dockit -d"aliasdd="dockit -c"aliasddd="dockit -cd"aliasdps="dockit -s"If you like my work, please consider buying me a coffee orPayPalThanks for your support! Cheers! 🎉