Many GitHub Actions workflows currently trigger on user forks, leading to
unnecessary CI resource consumption, unwanted bot behavior, and inevitable
failures. This commit restricts these specific workflows to only run on the
primary `containers/podman` repository.
The restricted workflows fall into two main categories:
1. Require Custom Upstream Secrets: Workflows like `release`, `mac-pkg`,
`cherry-pick`, and `dev-bump` rely on secrets (e.g., Apple/Azure certs,
PODMANBOT_TOKEN, ACTION_MAIL_*) that are unavailable in forks.
2. Manage Upstream Tracker State: Workflows like `assign`, `stale`, and
`labeler` are intended strictly for managing the primary project's
issues and PRs. Running them on personal forks creates unwanted noise.
Additionally, refactored several complex `if` conditions using YAML
multi-line strings (`|`) to maintain and improve readability.
Signed-off-by: Byounguk Lee <nimdrak@gmail.com>
When multiple containers in a pod YAML specify the same hostPort,
podman kube play previously accepted the YAML and started the
containers, causing one of them to fail at runtime with a confusing
bind() error.
Add early validation in getPodPorts() to detect duplicate
(hostIP, hostPort, protocol) tuples across containers and return
a clear error message naming both conflicting containers.
Fixes: https://github.com/podman-container-tools/podman/issues/26622
Signed-off-by: Miguel Álvarez <mialvare@redhat.com>
Add a Community Meetings section to README.md (under Communications)
listing all public Podman meetings available on the
LFX calendar:
- Podman Community Meeting: first Tuesday of even-numbered months,
11:00 a.m. Eastern — demos, announcements, and community updates
- Podman Standup (Monday): weekly at 10:00 a.m. Eastern, 30 min
- Podman Standup (Thursday): weekly at 11:00 a.m. Eastern, 30 min
Signed-off-by: Mohan Boddu <mboddu@redhat.com>
The services cannot be enables so we must not document this, instead
provide the proper pointer on what to do.
Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Add a warning that tests wipe local container state,
a quick-reference table of make targets,
and examples for running specific integration, machine,
system, and unit tests.
Signed-off-by: Jan Rodák <hony.com@seznam.cz>
Add ## descriptions to commonly used targets so they appear in make help.
Replace the `wc -L` column-width approach (unavailable on macOS without coreutils)
with awk-based alignment.
Signed-off-by: Jan Rodák <hony.com@seznam.cz>
Something with the cache is not working right and results in
inconsistent lint result.
Even on PRs where there are no source code changes we observe random
failures. I have seen at least 4 different instances since we the new CI
setup. It is not reasonable to spot fix each new warning (mostly just
adding new nolint comments) each time as it affects all PRs at once.
It will also be very confusing for new contributors.
Fixes: #28893
Signed-off-by: Paul Holzinger <pholzing@redhat.com>
As part of our move into the podman-container-tools org and our
migration to GH Actions CI, we moved several additional
repositories into the Podman Container Tools CNCF project. These
include container-libs (core libraries used by Podman and CRI-O),
podman-machine-os (builds OS images used by `podman machine`),
and automation (tools and scripts for maintaining our CI). All
of these went through the subproject process documented in our
governance and are now subprojects, so let's get them listed in
the governance.
Signed-off-by: Matt Heon <mheon@redhat.com>
FCOS symlinks /home to var/home. systemd rejects a mount unit whose
Where= path traverses a symlink, breaking default home dir mounts.
Resolve known FCOS symlinks before writing the ignition unit.
Fixes: #28911
Signed-off-by: Chanhyeok Seo <chanhyeok.seo@datadoghq.com>
For a while now we trigger CI tests based on if source files, i.e. *.go
files were changed. The "No New Tests" filter however checked something
else via a exclude list that was not being updated.
That means in many cases we needed to add the label when it is clear
that these thing should not need tests, i.e. packit or rpm/ changes.
To avoid the manual updates of all directories just grep for source
files.
Fixes: #28849
Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Only on Fedora there's a /bin/wait shell script that calls Bash's
builtin(1). This is not the case of openSUSE Tumbleweed with the same
Bash version and Debian 13. Otherwise we get errors from bats like:
BW01: `run`'s command `wait 872594` exited with code 127, indicating
'Command not found'. Use run's return code checks, e.g. `run -127`,
to fix this message.
Replace `run wait` with `wait || true` like it's done in other tests.
Signed-off-by: Ricardo Branco <rbranco@suse.de>
