-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Play Kube --log-opt causing panic #13356
Comments
@umohnani8 PTAL |
I can tackle this one (looking for some small issues until lunch break) |
Unassigning, this is not a quick-fix. Fixing the nil-deref is easy but it seems these options don't do what they are supposed to, so containers won't start anymore. |
A friendly reminder that this issue had no activity for 30 days. |
@cdoern PTAL |
I think I can figure out why the options are misfiring in such a drastic way. I will work on this tmrw |
@vrothberg I have put some debugs in here and it seems like adding a podman/libpod/oci_conmon_linux.go Lines 1406 to 1407 in c3d871a
I am trying to see how this is a larger issue beyond the nil pointer deref but can't seem to find a larger issue. Thoughts? |
@cdoern, looking at my earlier comment, containers didn't start anymore when I attempted to fix it. If that is not the case in your fix, that is good news :) |
currently tags cause a panic due to an uninitialized map. Initialize the map and add parsing to make sure we are only tagging with journald resolves containers#13356 Signed-off-by: cdoern <[email protected]>
currently tags cause a panic due to an uninitialized map. Initialize the map and add parsing to make sure we are only tagging with journald resolves containers#13356 Signed-off-by: cdoern <[email protected]>
currently tags cause a panic due to an uninitialized map. Initialize the map and add parsing to make sure we are only tagging with journald resolves containers#13356 Signed-off-by: cdoern <[email protected]>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Podman throwing an exception when run with
--log-opt tag="{{.ImageName}}"
Steps to reproduce the issue:
Install Debian 11 (Raspberry Pi OS Lite 64Bit 28.01.2022), update the system with
testing
repos and addexperimental
reposInstall Podman with
sudo apt -t experimental install podman
Run
podman play kube gitea-pod.yml --configmap=gitea-app-configmap.yml,gitea-db-configmap.yml --log-driver=journald --log-opt tag="{{.ImageName}}"
Describe the results you received:
Describe the results you expected:
An Running Pod with tags in journald logs
Additional information you deem important (e.g. issue happens only occasionally):
Other options like
--log-opt max-size=10mb,path=/var/log/mycontainer.json
do not raise an exception but also don't seem to work, because nothing is written to the file even when the Container puts out logs (file permissions are looking good).I used the following YAML to in the Command:
(The Config maps only contain secrets and env vars)
gitea-pod.yml
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: