Skip to content
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

Init Container keeps restarting while running using Quadlet-managed systemd units #18547

Closed
rrbanda opened this issue May 11, 2023 · 4 comments
Closed
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@rrbanda
Copy link

rrbanda commented May 11, 2023

Issue Description

When starting using systemctl start cube the service specified in Cube which is a K8S YAML file with an init container , the init container keeps restarting

Screenshot from 2023-05-11 17-34-16

Assumption

Systemd is flagging the init containers as failed, because they are treated identically to any other container and it is not aware that they aren't supposed to run continuously

Steps to reproduce the issue

Steps to reproduce the issue

  1. Run the services from this repo
  2. Look for container named minichris-cube-pod-migratedb which keeps restarting

Describe the results you received

Container restarts

Describe the results you expected

Once the init container peforms required tasks it should not restart and remaining containers should be up and running as expected

podman info output

If you are unable to run podman info for any reason, please provide the podman version, operating system and its version and the architecture you are running.

Podman in a container

Yes

Privileged Or Rootless

Privileged

Upstream Latest Release

Yes

Additional environment details

➜ podman -v
podman version 4.6.0-dev

on hypervisor ~ 
➜ cat /etc/os-release
NAME="Rocky Linux"
VERSION="8.7 (Green Obsidian)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="8.7"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Rocky Linux 8.7 (Green Obsidian)"
ANSI_COLOR="0;32"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:rocky:rocky:8:GA"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
ROCKY_SUPPORT_PRODUCT="Rocky-Linux-8"
ROCKY_SUPPORT_PRODUCT_VERSION="8.7"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.7"
on hypervisor ~ 

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

@rrbanda rrbanda added the kind/bug Categorizes issue or PR as related to a bug. label May 11, 2023
@rhatdan
Copy link
Member

rhatdan commented May 12, 2023

@vrothberg PTAL

@tony84727
Copy link
Contributor

Could be related to #18481

@vrothberg
Copy link
Member

Yes, after #18481 this issue is fixed. Sorry for the inconvenience.

@vrothberg
Copy link
Member

With #18481 having merged, we can close this issue.

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Aug 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

4 participants