-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
connection/podman.py broken on F34 #240
Comments
Yeah, it's probably best to start using |
Any way to temporarily make it work ? Tried replacing |
@JayDoubleu can you please provide a task that actually fails? It's not clear from the issue. Trying to reproduce now. |
@JayDoubleu please make sure you use actual collection with
This works for me in f34. |
It doesn't even get to tasks, it fails at gathering facts. # podman ps
#CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
#a95635f1fc42 registry.fedoraproject.org/fedora-toolbox:34 toolbox --verbose... 20 hours ago Up About an hour ago fedora-toolbox-34
- hosts: localhost
connection: local
tasks:
- name: Add toolbox as ansible host
add_host:
name: toolbox-default
ansible_host: "a95635f1fc42"
groups: toolbox
changed_when: false
- hosts: toolbox
connection: containers.podman.podman
gather_facts: true
vars:
ansible_python_interpreter: /usr/local/bin/python
tasks:
- name: Run tasks inside toolbox containers
template:
src: /tmp/aaa.j2
dest: ~/somefile1
On F33 on the other hand running below:- hosts: localhost
connection: local
vars:
ansible_python_interpreter: /usr/bin/python3
tasks:
- name: Add toolbox as ansible host
add_host:
name: toolbox-default
ansible_host: "783b054ce541"
groups: toolbox
changed_when: false
- hosts: toolbox
connection: containers.podman.podman
gather_facts: true
vars:
ansible_python_interpreter: /usr/bin/python3
tasks:
- name: Run tasks inside toolbox containers
template:
src: /tmp/aaa.j2
dest: ~/somefile1 Returns:
|
@sshnaidm Interesting.. This seems to be toolbox related. I just created a simple container with Should I bother folks over @containers/toolbox? |
@JayDoubleu yeah, it seems related to how you create the container. I just ran |
Well, seems like toolbox mounts the whole home directory: "Mounts": [
{
"Type": "bind",
"Source": "/home/fedora",
"Destination": "/home/fedora",
"Driver": "",
"Mode": "",
"Options": [
"rbind"
],
"RW": true,
"Propagation": "rslave"
},
and short reproducing is:
Maybe toolbox folks know what is the problem, or |
This seems to be podman issue containers/podman#9985 |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Unable to use podman connection on F34
operation not permitted
Steps to reproduce the issue:
Describe the results you received:
Every play fails with not permitted error
Additional information you deem important (e.g. issue happens only occasionally):
Version of the
containers.podman
collection:1.5.0
1.4.4
Either git commit if installed from git:
git show --summary
Or version from
ansible-galaxy
if installed from galaxy:ansible-galaxy collection list | grep containers.podman
Output of
ansible --version
:Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Playbok you run with ansible (e.g. content of
playbook.yaml
):Command line and output of ansible run with high verbosity
Please NOTE: if you submit a bug about idempotency, run the playbook with
--diff
option, like:ansible-playbook -i inventory --diff -vv playbook.yml
Additional environment details (AWS, VirtualBox, physical, etc.):
Fedora Silverblue 34
Managed to get past
podman unshare
error by altering podman.py with:However it sill fails with below:
The text was updated successfully, but these errors were encountered: