Bug 1372487 - What if the systemd is started from a wrapper script?
Summary: What if the systemd is started from a wrapper script?
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: oci-systemd-hook
Version: 24
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-01 23:02 UTC by Peter Schiffer
Modified: 2016-09-02 20:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-02 20:28:58 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Peter Schiffer 2016-09-01 23:02:36 UTC 
Description of problem:
I have a container running systemd inside, but before starting the systemd I'm running shell script, which prepares the environment, set up db, etc.. and in the end, it runs:
exec /usr/sbin/init

In this case, the oci-systemd-hook doesn't recognize the systemd inside of the container, because the CMD in Dockerfile is: CMD [ "/docker-cmd.sh" ]

Version-Release number of selected component (if applicable):
oci-systemd-hook-0.1.4-1.fc24.x86_64
Comment 1 Daniel Walsh 2016-09-02 10:20:46 UTC 
If you change the name of your script to /init, I think it will work.
oci-systemd-hook is looking for executables named init or systemd
Comment 2 Peter Schiffer 2016-09-02 20:28:58 UTC 
Thanks, renaming shell script to /init worked.
Note You need to log in before you can comment on or make changes to this bug.