docker-pipeline | Python tool to run docker containers | BPM library

by Duke-GCB Python Version: 0.9.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | docker-pipeline Summary

docker-pipeline is a Python library typically used in Automation, BPM, Docker applications. docker-pipeline has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

Python tool to run docker containers in sequence, for reproducible computational analysis pipelines

Support

Quality

Security

License

Reuse

Support

docker-pipeline has a low active ecosystem.

It has 10 star(s) with 0 fork(s). There are 7 watchers for this library.

It had no major release in the last 12 months.

There are 5 open issues and 8 have been closed. On average issues are closed in 16 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of docker-pipeline is 0.9.0

Quality

docker-pipeline has no bugs reported.

Security

docker-pipeline has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

docker-pipeline is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

docker-pipeline releases are available to install and integrate.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed docker-pipeline and discovered the below as its top functions. This is intended to give you an instant insight into docker-pipeline implemented functionality, and help decide if they suit your requirements.

Configure YAML loader .
Run the pipeline .
Translate local path to remote
Make a dictionary of volumes .
Get the result of a container .
Parse a mount specification .
Return True if path can access the given permission .
Extracts the values from the leftovers .
Main entry point .
Return the string representation of the pipeline .

Get all kandi verified functions for this library.

docker-pipeline Key Features

No Key Features are available at this moment for docker-pipeline.

docker-pipeline Examples and Code Snippets

No Code Snippets are available at this moment for docker-pipeline.

Community Discussions

Trending Discussions on docker-pipeline

Is Jenkins running command inside container?

Jenkins does not wait for docker exec command to complete

How do I keep the local docker image made by Jenkins?

Jenkins Docker pipeline plugin refers to old JENKINS_HOME

QUESTION

Is Jenkins running command inside container?

Asked 2020-Mar-31 at 07:16

I want to run the Jenkins pipeline inside a docker container, like running all the tests, doing sonar scanning, etc.

This is what my pipeline looks like.

...

ANSWER

Answered 2020-Mar-31 at 06:34

After carefully looking at the logs of the pipeline job I saw this line

Source https://stackoverflow.com/questions/60928664

QUESTION

Jenkins does not wait for docker exec command to complete

Asked 2020-Feb-19 at 16:55

Here's the situation:

I have a docker container (jenkins). I've mounted the sockets to my container so that I can perform docker commands inside my jenkins container.

Manually, everything works in the container. However, when Jenkins executes the job, it doesn't "wait" for the docker exec command to run to completion.

Below, is an extract from the Jenkinsfile. The short-lived printenv command runs correctly, and prints the environment variables. The next command (python) just gets run and then Jenkins moves on immediately, not waiting for completion. The Jenkins agent (slave) is running on an Ubuntu image. Running all these commands outside Jenkins work as expected.

...

ANSWER

Answered 2020-Feb-19 at 15:36

Ugh. This was down to the way that I'd set up docker support on the slave container.

I'd used socat to provide a TCP server proxy. Instead, switched that out for a plain old docker.sock volume between host & container.

Source https://stackoverflow.com/questions/60285942

QUESTION

How do I keep the local docker image made by Jenkins?

Asked 2019-Nov-15 at 19:14

Jenkins with docker-pipeline is downloading my git repository, and installing it.

...

ANSWER

Answered 2019-Nov-15 at 19:13

You may want to use dockerfile agent instead of the docker one. It uses a Dockerfile that is part of your project to build the local docker image. All image layers will be cached, so the next time you run the build, it won't spend time on re-building the image. It is also useful to put commands like npm install -production inside the Dockerfile, so those dependencies are downloaded and installed only one time.

Take a look at the following example.

Dockerfile:

Source https://stackoverflow.com/questions/58882548

QUESTION

Jenkins Docker pipeline plugin refers to old JENKINS_HOME

Asked 2019-Jan-23 at 15:02

I recently ran into my disk limits on a Jenkins server. I decided to solve this permanently by mounting a larger volume and move the Jenkins home directory to that volume. I used this wiki page as a reference for the move: https://wiki.jenkins.io/display/JENKINS/Administering+Jenkins. I am using init.d to start Jenkins and changed the JENKINS_HOME directory in /etc/default/jenkins (the init script refers to this location to get its defaults).

After rebooting Jenkins I could confirm it was running in the new Home directory. My build works initially (scm checkout->docker build->test->push to docker registry). However, when arriving at the push stage, an error is generated saying that the directory /var/lib/jenkins could not be created. This is the old JENKINS_HOME (as the new JENKINS_HOME is set at /mnt/jenkins). The full stacktrace can be seen below.

What did I miss here? Is there another setting relevant in the move? I am using the docker-commons and docker-pipeline plugins. Any help is highly appreciated.

...

ANSWER

Answered 2019-Jan-23 at 15:02

TLDR; Solution: Move any credential files and dirs back to the original location OR change the jenkins user home dir [usermod -d /new/dir jenkins] (this is what I have done). Make sure to move the files out of the way first as the usermod command cannot be run on an existing directory.

After some fiddling around I found the issue. Maybe this is helpful for others.

The jenkins users' home directory was still set at /var/lib/jenkins. This is the directory where the credentials for dockerhub are stored. During the job, Jenkins tried to access the credentials on the old location because by default it looks in the jenkins user home directory.

Source https://stackoverflow.com/questions/54325614

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install docker-pipeline

Installing and running via Docker is recommended.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: