Skip to content

Conversation

@lisongmin
Copy link
Contributor

This PR reduces services downtime by pulling images before teardown containers on up command.

@lisongmin lisongmin force-pushed the feat-pull-before-teardown branch from 86de1ab to 276a781 Compare August 27, 2025 10:45
Signed-off-by: Songmin Li <lisongmin@protonmail.com>
When both image and build section exist,
and the image starts with "localhost/", podman-compose
tries to pull the image, which is not expected.

Signed-off-by: Songmin Li <lisongmin@protonmail.com>
@Qwarctick
Copy link

Seems good. Why this is not yet merged?

log.error("Build command failed")
if not args.dry_run:
return build_exit_code
return build_exit_code
Copy link
Collaborator

Choose a reason for hiding this comment

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

Rather large commit just to fix pylint warnings

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I got the following warning from pylint:

podman_compose.py:3215:12: W1203: Use lazy % formatting in logging functions (logging-fstring-interpolation)
podman_compose.py:3220:12: W1203: Use lazy % formatting in logging functions (logging-fstring-interpolation)
podman_compose.py:3283:0: R0911: Too many return statements (7/6) (too-many-return-statements)

And since build image and pull image are both prepare images before running, I split it out to the prepare_images.

Any idea to fix the warning with less changes?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi, p12tic,

I just split the last commit into two commits, but i don't know if this is what you want.
Please check it.

Signed-off-by: Songmin Li <lisongmin@protonmail.com>
Signed-off-by: Songmin Li <lisongmin@protonmail.com>
@lisongmin lisongmin force-pushed the feat-pull-before-teardown branch from 276a781 to 3a42866 Compare November 6, 2025 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants