containers
/
podman
mirror of https://github.com/containers/podman.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
18,412 Commits 52 Branches 247 Tags 253 MiB
Commit Graph

5 Commits

Author SHA1 Message Date
Boaz Shuster 7cfe0328f1 Add support to sig-proxy for podman-remote 
Signed-off-by: Boaz Shuster <boaz.shuster.github@gmail.com>
 2022-09-20 22:52:45 +03:00
Doug Rabson 66c62eb968 Implement CatchAll and StopCatch in signal_common.go 
This is part of a set of changes to port podman to the FreeBSD platform.
The pkg/signal parts are needed to enable ABI mode on FreeBSD. No tests
are needed here because it should be a functional no-op for linux.

[NO NEW TESTS NEEDED]

Signed-off-by: Doug Rabson <dfr@rabson.org>
 2022-06-27 13:27:12 +01:00
Paul Holzinger 70f147d019
cmd/podman/common/completion.go: fix FIXMEs 
There is no good way to recommend labels for podman container runlabel.

Add the missing max-size log option. These are the only documented
options so the completion should not suggest something different.

Add proper --stop-signal completion. It will now complete all supported
signal names both upper and lowercase depending on the user input. Also
it work with and without the SIG prefix.

Fixing the TODOs in this file are more complicated since they describe
bigger features.

[NO NEW TESTS NEEDED]

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
 2022-05-24 17:56:37 +02:00
Valentin Rothberg 6c030cd573 fix a number of `godot` issues 
Still an unknown number remains but I am running out of patience.
Adding dots is not the best use of my time.

Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
 2022-03-22 13:04:35 +01:00
Matthew Heon e0eb6022b3 Ensure that signal names can be parsed on Windows 
To ensure the Windows and OS X remote clients can properly parse
container stop signal (when given as a name e.g. SIGTERM) and
set it in SpecGen, we need access to a list of Linux signal names
and the numbers they map to that is available on non-Linux OSes.
Fortunately, these are ABI constants that are extremely unlikely
to change, so we can just take the existing constant definitions
from the library and use them.

The signal numbers used here are sourced from AMD64, but should
be the same for every architecture that is not Alpha, SPARC,
MIPS, and PA-RISC. So `podman run --stop-signal SIGTTOU` from a
Windows client to a Podman service on a SPARC host will set an
incorrect stop signal, but I don't think this is a large problem.

Signed-off-by: Matthew Heon <mheon@redhat.com>
 2020-05-28 14:26:36 -04:00