By the way,I have shrinked a bit ansible.log, you can find it here:It looks like containers are going up, and I see them being up.but when I exec:[root@remote-u stack]# podman run -it d7b8f19cc5ed /bin/bash
Error: error configuring network namespace for container 0f5d43e509f3b673180a677e192dd5f2498f6061680cb0db9ae15d739c2337e3: Missing CNI default network
[root@remote-u stack]#I get this interesting line, should I get it?also, here is my undercloud.conf:also, as I mentioned, previously, paunch.log is empty, I have added +w to it but it still empty.[root@remote-u stack]# cat /var/log/paunch.log
[root@remote-u stack]# ls -la /var/log/paunch.log
-rw-rw-rw-. 1 root root 0 Apr 28 10:59 /var/log/paunch.log
[root@remote-u stack]#And I do not have proxy, luckily. but on another site, where we have proxy we face similar issues. and fails on same place.On Wed, 29 Apr 2020 at 12:02, Wu, Heng <wuh.fnst@cn.fujitsu.com> wrote:> I am new to containers, can I somehow transfer these images between, as I understand, it might help?
The image will be downloaded automatically with the installation, you don't need to do it manually.
The problem seems to be that the container failed to start, not the errors in the images themselves.
You may need to check the configuration of undercloud.conf and proxy settings (if they exist).