Commit Graph

5 Commits

Author SHA1 Message Date
Pratik Raj 952e881922
optimize size and time using --no-cache-dir
Using --no-cache-dir flag in pip install ,make sure dowloaded packages
by pip don't cached on system . This is a best practise which make sure
to fetch ftom repo instead of using local cached one . Further , in case
of Docker Containers , by restricing caching , we can reduce image size.
In term of stats , it depends upon the number of python packages
multiplied by their respective size . e.g for heavy packages with a lot
of dependencies it reduce a lot by don't caching pip packages.

Further , more detail information can be found at

https://medium.com/sciforce/strategies-of-docker-images-optimization-2ca9cc5719b6

Change-Id: Ia635ecb0eaea3a400a0b03031efec354d0c3c77e
Signed-off-by: Pratik Raj <rajpratik71@gmail.com>
2020-10-03 11:52:16 +05:30
Hongbin Lu c528e9be2f Replace port 35357 with port 5000
Starting from Keystone v3, the port 35357 is not used.
See: https://review.opendev.org/#/c/541857/

Change-Id: I4fee6ebcca6cbb1c610fa19c4294ef5a45b50709
2019-04-29 22:17:03 +00:00
Liping Mao (limao) 0dd2ad15af Kuryr-libnetwork Docker managed plugin
This patch add a script to create v2plugin rootfs.
1. use local unix socket for v2plugin
2. add config.json for v2plugin
3. Add scripts to build v2plugin rootfs
4. Update devstack to use v2plugin

Change-Id: I91d352a963840f33d1d2f9cea17ab6ac777d22bc
Related-Bug: #1668486
Partially-Implements: BP docker-v2plugin
2017-05-03 08:58:54 +08:00
Liping Mao (limao) 95e22ab2b6 Kuryr-libnetwork container ssl error in multi-thread
When use kuryr-libnetwork container with multi-thread and neutron
service under https, uwsgi will has ssl error.

Change-Id: I897d84742570dcc2d4daba1ea40882814a38679f
Related-Bug: #1675301
2017-03-24 14:26:55 +08:00
Antoni Segura Puimedon 6f6ff11645
container: Build the container from tree not git
Up until this patch, the Docker container for the Kuryr libnetwork
daemon was part of contrib and was being built by checking out the
latest master from github. That is not very helpful when developers
want to build the container to run their latest changes.

With this change, we move the Docker building to the root of the repo so
that it can use the current state of the repo to build and update the
README.rst to contain the information relative to building and using the
container.

Change-Id: Ie9032d62c73d873a29cabe84c64a19df13fdb749
Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
2016-09-14 10:23:12 +02:00