CONTAINERS Archives - scmGalaxy

Docker malformed HTTP status code “online”

scmgalaxy K — Sat, 09 Dec 2017 11:39:28 +0000

rajeshkumar created the topic: Docker malformed HTTP status code “online”

Error

[root@localhost madhavi]# docker pull jenkins
Using default tag: latest
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon. Is the docker daemon running on this host?). Using system default: index.docker.io/v1/ 
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
[root@localhost madhavi]# systemctl start docker
[root@localhost madhavi]# docker pull jenkins
Using default tag: latest
Pulling repository docker.io/library/jenkins
Error while pulling image: Get index.docker.io/v1/repositories/library/jenkins/images : malformed HTTP status code "online"
[root@localhost madhavi]#

Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Docker malformed HTTP status code “online” appeared first on scmGalaxy.

Docker Toolboox error in Windows

scmgalaxy K — Sat, 09 Dec 2017 11:37:27 +0000

rajeshkumar created the topic: Docker Toolboox error in Windows

Error
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.26/info: open
//./pipe/docker_engine: The system cannot find the file specified. In the defau
lt daemon configuration on Windows, the docker client must be run elevated to co
nnect. This error may also indicate that the docker daemon is not running.

Solution
stackoverflow.com/questions/37527888/doc…nds-fails-in-windows

The following environment properties need to be set:
set DOCKER_CERT_PATH=%USERPROFILE%\.docker\machine\machines\default
set DOCKER_HOST=tcp://192.168.99.100:2376
set DOCKER_MACHINE_NAME=default
set DOCKER_TLS_VERIFY=1

$ docker-machine rm default
$ docker-machine create –driver virtualbox default

Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Docker Toolboox error in Windows appeared first on scmGalaxy.

Docker Command line Reference | Docker Tutorial | Docker Guide

scmgalaxy K — Fri, 15 Jul 2016 17:50:41 +0000

One liner to stop all of Docker containers:

> docker stop $(docker ps -a -q)

One liner to remove all of Docker containers:

> docker rm $(docker ps -a -q)

> docker rm $(docker images -q)

> docker rmi $(docker images -q)

In case of error message Get http:///var/run/docker.sock/v1.14/containers/json?all=1: dial unix /var/run/docker.sock: permission denied

> sudo docker rm $(sudo docker ps -a -q)

To only stop exited containers and delete only non-tagged images.:

> docker ps –filter ‘status=Exited’ -a | xargs docker stop

> docker images –filter “dangling=true” -q | xargs docker rmi

Remove all containers that aren’t currently running:

> docker rm $(docker ps -a -q -f “status=exited*”)

if not the volumes will not be delete !!! (like if you are using a mysql docker image) and all the volumes will be orphans !

> sudo docker rm -f -v $(sudo docker ps -a -q)

The post Docker Command line Reference | Docker Tutorial | Docker Guide appeared first on scmGalaxy.

Simple Docker workflow – Quick start | Docker Tutorial

scmgalaxy K — Tue, 23 Feb 2016 15:17:33 +0000

Simple Docker workflow – Quick start

In this tutorials, I am trying to cover the simple quickstart Docker workflow and for the example, I am creating Ubantu containee and using it to showcase this tutorial.

Step 1 – Download the Ubantu image container from the Docker Hub

# docker pull -a ubuntu

Step 2 – Run the ubuntu container and access to ther /bin/bash commands prompt

# docker run -it ubuntu /bin/bash

Step 3 – Stop the container

# docker stop container_id

How to get the container id?

# docker ps -a

Step 4: Start the container again?

# docker start container_id

Step 5: Exit the running container without stopping the container

# exit

Step 6: Login the running container for bash prompt

# sudo docker exec -i -t 2e56ad1705b1 /bin/bas

For more – Refer

http://www.scmgalaxy.com/scm/package-management/how-to-get-bash-or-ssh-into-a-running-container-in-background-mode.html

The post Simple Docker workflow – Quick start | Docker Tutorial appeared first on scmGalaxy.

How to get bash or ssh into a running container in background mode?

scmgalaxy K — Tue, 23 Feb 2016 11:51:34 +0000

How to get bash or ssh into a running container in background mode?

Step 1: First of all, try to find your active container by running

# docker ps

# docker ps -a

Step 2: If the container is not running,

# docker start your_id

Step 3: If we use attach we can use only one instance of shell.

# sudo docker attach 665b4a1e17b6 #by ID

# sudo docker attach loving_heisenberg #by Name

If we want open new terminal with new instance of container’s shell, we just need run the following:

# sudo docker exec -i -t 2e56ad1705b1 /bin/bash #by ID

# sudo docker exec -i -t loving_heisenberg /bin/bash #by Name

# root@665b4a1e17b6:/#

Step 4: To exit bash without leaving bash running in a rogue process

# exit

Notes:

A reminder for boot2docker users: remove sudo

If you are using docker in Linux, you will have to use sudo along with docker commands.

You should try not to run commands as sudo, rather add your user to the docker group and just run normally.

The post How to get bash or ssh into a running container in background mode? appeared first on scmGalaxy.

How to install Atlassian Jira using Docker?

scmgalaxy K — Tue, 23 Feb 2016 11:32:56 +0000

Install Atlassian Jira using Docker

Download and Run the jira latest:

# docker run –detach –publish 8080:8080 cptactionhank/atlassian-jira:latest

Then simply navigate your preferred browser to http://[dockerhost]:8080 and finish the configuration.

Notes:

JIRA Home location: /var/atlassian/jira

JIRA Installation location: /opt/atlassian/jira

Reference:

https://hub.docker.com/r/cptactionhank/atlassian-jira/

The post How to install Atlassian Jira using Docker? appeared first on scmGalaxy.