Skip to content

Conversation

@hqhq
Copy link
Contributor

@hqhq hqhq commented Jan 8, 2016

Fixes: #438

Signed-off-by: Qiang Huang [email protected]

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggest use this:

factory, err := libcontainer.New("/var/lib/container", libcontainer.Cgroupfs, libcontainer.InitArgs(os.Args[0], "init"))

It can help more understood, it would can init() during cmd run

@hqhq hqhq force-pushed the hq_fix_libcontainer_readme branch from d06c5e7 to d87ac4a Compare January 14, 2016 06:54
@hqhq
Copy link
Contributor Author

hqhq commented Jan 14, 2016

@HackToday Updated, thanks.

@HackToday
Copy link
Contributor

looks OK. Although not a maintainer, but I think I can vote use 👍

@LK4D4
Copy link
Contributor

LK4D4 commented Jan 15, 2016

I think it's a great change. Thanks!
LGTM

LK4D4 added a commit that referenced this pull request Jan 15, 2016
@LK4D4 LK4D4 merged commit f2f8f0e into opencontainers:master Jan 15, 2016
@hqhq hqhq deleted the hq_fix_libcontainer_readme branch January 18, 2016 01:14
stefanberger pushed a commit to stefanberger/runc that referenced this pull request Sep 8, 2017
Add a 'status' field to our state struct
stefanberger pushed a commit to stefanberger/runc that referenced this pull request Sep 8, 2017
In [1], I'd proposed replacing our old "user-specified process" with
"user-specified code" to help distinguish between 'create' (cloning
the container process) and 'start' (signaling the container process to
execve or similar the user-specified $STUFF_FROM_THE_process_CONFIG).
That PR was rejected, although the renaming proposed there had already
landed via dd0cd21 (Add a 'status' field to our state struct,
2016-05-26, opencontainers#462).

This PR attempts to find a common ground between "process" (preferred
by maintainers in opencontainers#466 [2,3,4], but which I consider incorrect [5])
and "code" (which maintainers found confusing [3,4,6]).  The Linux
execve(2) says "program" and unpacks that to "a binary executable, or
a script starting with a [shebang]" [7].  proc(5) documents
/proc/[pid]/exe by talking about "the executed command" [8].  The
POSIX exec docs call this the "process image" and talk about loading
it from the "new process image file" (although they also sprinkle in a
number of “program” references, apparently interchangeably with
“process image”) [9].

POSIX formally defines "command" [11], "executable file" [12], and
"program" [13].  The only reference to "process image" in the
definitions is in the "executable file" entry.  The "command"
definition is focused on the shell, the "executable file" definition
is focused on files, and the "program" definition talks about a
"prepared sequence of instructions to the system", so "program" seems
like the best fit.

[1]: opencontainers/runtime-spec#466
     Subject: runtime: Replace "user-specified process" with "user-specified code" in 'create'
[2]: opencontainers/runtime-spec#466 (comment)
[3]: opencontainers/runtime-spec#466 (comment)
[4]: opencontainers/runtime-spec#466 (comment)
[5]: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_295
[6]: opencontainers/runtime-spec#466 (comment)
[7]: http://man7.org/linux/man-pages/man2/execve.2.html
[8]: http://man7.org/linux/man-pages/man5/proc.5.html
[9]: http://pubs.opengroup.org/onlinepubs/9699919799/functions/exec.html
[10]: https://git.kernel.org/cgit/docs/man-pages/man-pages.git/
[11]: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_104
[12]: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_154
[13]: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_306

Signed-off-by: W. Trevor King <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants