Does docker restart use the latest image or the one the container was created with?


yodude7
25/12/2015 9:47 am
HOME ยป Network & Servers

If I create a container using a tag/label

docker run --name some_container -d me/my_image

Update the image with

docker pull me/my_image

And restart the container with

docker restart some_container

Which version does the new container use?

In docker inspect .Image gives the id of the specific image, .Config.Image gives the label.


Related to : Does docker restart use the latest image or the one the container was created with?
Does docker restart use the latest image or the one the container was created with?
25/12/2015 9:47 am Network & Servers

If I create a container using a tag/label

docker run --name some_container -d me/my_image

Update the image with

docker pull me/my_image

And restart the container with

docker restart some_container

Which version does the new container use?

In docker inspect .Image gives the id of the specific image, .Config.Image gives the label.


UDP Traffic from outside to docker container is dropped after container restart
19/12/2014 10:06 am Network & Servers

following situation: i have a hardware box with Ubuntu 14.04LTS as host for docker 1.4 I'm running an ELK stack in several containers. Curenntly the logstash container is exposing only port 514 to collect syslog input.

in some situations, after restarting the container, syslog traffic is not forwarded to the container anymore.

'iptables -nvL' shows that there is no traffic matching the rule applied to the forwarding chain during container start. The traffic counter of the INPUT chain is considerably higher than in the FORWARD chain.

I notice this behavior on all containers that are exposing UDP ports to the world, containers with TCP based services are working as expected.

restarting the containers and the docker service is without success.

I'm mainly collecting firewall trafficlogs, so the syslog traffic flow is quite constant. I'm collecting approx 1,5k Syslog traps per second.

My workaround here is to stop all traffic to the host for about 10 seconds (currently by blackholing the traffic on an upstream router)

After stopping syslog export on one single firewall node for a few seconds, traffic from this specific firewall is forwarded to the container as expected. But only from this single one.

I think that this is an issue of iptables. It seems that iptables is caching the forwarding-infrmation for a few seconds and is ignoring any new applied rules as long as traffic is present.

I've done no additional configuration on iptables here. Everything is done by docker. I have no ufw, conntrackd or anything installed.

Any suggests how to solve this issue?

best regards Andreas


How can I stop and delete a docker container launched with restart always option?
4/12/2014 2:10 am Network & Servers

I run some containers with the option --restart always.

It works good, so good, that I have now difficulties to stop these containers now :)

I tried :

sudo docker stop container && sudo docker rm -f
container

But the container still restarts.

The docker documentation explains the restart policies, but I didn't find anything to resolve this issue.


Cloudera support for docker container or Docker support for CM 5 image
10/12/2014 6:20 pm Network & Servers

Recently my org is considering Docker. Our group is using cloudera CDH 5.1.2.

1) Does cloudera compatable with Docker container? 2) Is there any known issue related to docker and cloudera combination?

I could not find any topic on docker in this forum.

Any pointer would be helpful.

Thanks, Amit




HD Wallpapers
3D
3D Abstract
City
Celebrities
Indian Celebrities
Cars
Travel
Girls
Animals Birds
Movies
Sports
Black White
Nature
Planes
Anime
Food Drink
Dreamy Fantasy
Architecture
Games
Space
Holidays
Flowers
Love
Artistic
Baby
Beach
Bikes Motorcycles
Macro
Computers
Vector
Funny
Army
Textures
Brands
Misc
Music
Other
Privacy Policy - Copyrights Notice - Feedback - Report Violation - RSS 2017 © bighow.org All Rights Reserved .