All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amy Fong <amy.fong@windriver.com>
To: meta-virtualization@yoctoproject.org, amy.fong@windriver.com
Subject: [PATCH] docker-registry invalid path on startup
Date: Wed, 22 Jul 2015 12:12:28 -0400	[thread overview]
Message-ID: <20150722161227.GA31716@windriver.com> (raw)

From 383cba6388cf7a1a221a0b03b78d017b0f0fe299 Mon Sep 17 00:00:00 2001
From: Amy Fong <amy.fong@windriver.com>
Date: Wed, 22 Jul 2015 10:43:14 -0400
Subject: [PATCH] docker-registry invalid path on startup

Systemd throws the following warning at boot:
systemd[1]: [/lib/systemd/system/docker-registry.service:10]
	Not an absolute path, ignoring: #WORKDIR#

Fix WORKDIR in docker-registry's systemd from #WORKDIR# to
${PYTHON_SITEPACKAGES_DIR}/docker_registry

Signed-off-by: Amy Fong <amy.fong@windriver.com>
---
 recipes-containers/docker-registry/docker-registry_git.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/recipes-containers/docker-registry/docker-registry_git.bb b/recipes-containers/docker-registry/docker-registry_git.bb
index 338cb69..fe766d2 100644
--- a/recipes-containers/docker-registry/docker-registry_git.bb
+++ b/recipes-containers/docker-registry/docker-registry_git.bb
@@ -83,6 +83,7 @@ do_install_append() {
 	if ${@base_contains('DISTRO_FEATURES','systemd','true','false',d)}; then
 		install -d ${D}${systemd_unitdir}/system
 		install -m 644 ${WORKDIR}/docker-registry.service ${D}/${systemd_unitdir}/system
+		sed -i "s|#WORKDIR#|${PYTHON_SITEPACKAGES_DIR}/docker_registry|" ${D}/${systemd_unitdir}/system/docker-registry.service
 	fi
 	# based on config_mirror.yml - uses /var/docker-registry instead of /tmp for files
 	install ${WORKDIR}/config.yml ${D}/etc/docker-registry.yml
-- 
2.1.4



             reply	other threads:[~2015-07-22 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 16:12 Amy Fong [this message]
2015-07-22 20:13 ` [PATCH] docker-registry invalid path on startup Bruce Ashfield

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150722161227.GA31716@windriver.com \
    --to=amy.fong@windriver.com \
    --cc=meta-virtualization@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.