New idempotency issue when using Podman 2 on Ubuntu #68
Assignees
Labels
Milestone
Comments
|
@jaudriga I'm trying to reproduce it with ubuntu 20, but can't now. Do you have specific Apparmor settings? What is your network setup for containers? |
|
@jaudriga any news about it? Is it still an issue? |
|
I'm having the same issue, yes. Maybe it only happens with root podman? |
|
Yeah, I found reproducing of "bridge" issue in #80 . In root containers default network mode is |
|
OK, I got it reproduced finally, happens with root on ubuntu 20 and podman 2.0.2 |
sshnaidm
added
bug
Merged
sshnaidm
added a commit
that referenced
this issue
Jul 16, 2020
Fix idempotency issues in podman_container Add creating workdir, buildah issue: containers/buildah#2475 Fix #68 Fix #69 Should help to #80 as well, but will be handled separately.
|
This seems to be still happening. According to my tests, this happens when you add the container to a pod that had open ports. playbook- name: add ubuntu host
hosts: localhost
tasks:
- name: add ubuntu 20.04 host
add_host:
ansible_host: "192.168.122.207"
name: ubuntu
- name: test
hosts: ubuntu
collections:
- containers.podman
tasks:
- name: create pod
podman_pod:
name: traefik_pod
publish:
- "10080:10080"
- "10443:10443"
- &container
name: start traefik container
podman_container:
image: docker.io/library/traefik:2.2
name: traefik
pod: traefik_pod
restart_policy: unless-stopped
state: started
command:
- --entryPoints.web-insecure.address=:10080
- --entryPoints.web-main.address=:10443
- --entryPoints.web-main.http.tls=true
- --log.level=DEBUG
- --providers.file.directory=/etc/traefik/dynamic
- --providers.file.watch=true
- *container
- name: remove traefik pod
podman_pod:
name: traefik_pod
state: absentExecution resultsYou can see that ubuntu host had 4 changed tasks instead of 3 as expected, because both calls to create container were reported as changed. The ubuntu machine is a simple VM booted with GNOME Boxes. I'm using containers.podman 1.1.2. Running the playbook agains localhost directly (Fedora 32 Silverblue) produces the expected behavior. |
|
@yajo can you please rerun it with |
|
Yes, it seems fixed, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Idempotency is broken once again similar to #31 , but this time for
networkandsecurity_opt(apparmor).Steps to reproduce the issue:
Run it
Run it again
Describe the results you received:
It recreates the container. Using
-Done can see why:Describe the results you expected:
No rebuild of the container.
Additional information you deem important (e.g. issue happens only occasionally):
I can reproduce this for all of my containers.
Output of
ansible --version:Output of
podman version:Output of
podman info --debug:Package info (e.g. output of
rpm -q podmanorapt list podman):Playbok you run with ansible (e.g. content of
playbook.yaml):See above.
Command line and output of ansible run with high verbosity:
Additional environment details (AWS, VirtualBox, physical, etc.):
Ubuntu 20.04 on AWS
The text was updated successfully, but these errors were encountered: