WordPress loopback error

Support
,
2

It seems the loopback tests want to access the host which is not allowed when using the default rootless podman pasta network.

You could edit the service file to use the slirp4netns network including the allow_host_loopback option: (Assuming the wordpress app instance is named wordpress1)

runagent -m wordpress1 systemctl --user edit --full wordpress

Add the network option to the podman pod create command:

...
ExecStartPre=/usr/bin/podman pod create --infra-conmon-pidfile %t/wordpress.pid \
    --pod-id-file %t/wordpress.pod-id \
    --network=slirp4netns:allow_host_loopback=true \
    --name wordpress \
    --publish 127.0.0.1:${TCP_PORT}:80 \
    --replace
...

Restart wordpress to apply the new option:

systemctl restart user@$(id -u wordpress1).service

Thanks for pointing out, I think we should include it to the wordpress app so it will survive updates, I’m going to open an issue tomorrow…

EDIT:

2 Likes