kuryr-libnetwork docker image did not output

Bug #1670063 reported by Liping Mao
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kuryr-libnetwork
Fix Released
Undecided
Unassigned

Bug Description

We have the following guide to run kuryr-libnetwork container image:
https://github.com/openstack/kuryr-libnetwork#how-to-run-the-container

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
sudo mkdir -p /usr/lib/docker/plugins/kuryr
sudo curl -o /usr/lib/docker/plugins/kuryr/kuryr.spec \
https://raw.githubusercontent.com/openstack/kuryr-libnetwork/master/etc/kuryr.spec
sudo service docker restart

Then we start the container::

docker run --name kuryr-libnetwork \
  --net=host \
  --cap-add=NET_ADMIN \
  -e SERVICE_USER=admin \
  -e SERVICE_PROJECT_NAME=admin \
  -e SERVICE_PASSWORD=admin \
  -e SERVICE_DOMAIN_NAME=Default \
  -e USER_DOMAIN_NAME=Default \
  -e IDENTITY_URL=http://127.0.0.1:35357/v3 \
  -v /var/log/kuryr:/var/log/kuryr \
  -v /var/run/openvswitch:/var/run/openvswitch \
  kuryr/libnetwork
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

But the log did not output into /var/log/kuryr. This is because we did not configure in /etc/kuryr/kuryr.conf:
log_dir = /var/log/kuryr
log_file = kuryr.log

Liping Mao (limao)
description: updated
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kuryr-libnetwork (master)

Reviewed: https://review.openstack.org/441645
Committed: https://git.openstack.org/cgit/openstack/kuryr-libnetwork/commit/?id=f96605c9d54776ed55615295c02e32dd9754201e
Submitter: Jenkins
Branch: master

commit f96605c9d54776ed55615295c02e32dd9754201e
Author: Liping Mao (limao) <email address hidden>
Date: Sun Mar 5 13:02:09 2017 +0800

    Add default log_file and log_dir in kuryr-libnetwork docker image

    Change-Id: Ibe308dd30eed17f0183edaa9cb44fab9e43cd852
    Closes-bug: #1670063

Changed in kuryr-libnetwork:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.