I would like to enhance the AIO compatibility with podman. Are the some development docs about the mastercontainer?

[aanno]

Hello,

I looked into the problems of AIO with podman a bit. I've got the impression that adding --add-host <your-nextcloud-aio-fq-domain>:host-gateway would improve things substantial.

However I'm new to the AIO mastercontainer and its PHP code. AFAIK, the mastercontainer controls starting the other containers by using docker unix socket.

I would like to interfere here and test my idea. Is there some docs about mastercontainer development? Where is the place where the PHP code starts new containers?

Kind regards, aanno

[szaimen]

Hi,

However I'm new to the AIO mastercontainer and its PHP code. AFAIK, the mastercontainer controls starting the other containers by using docker unix socket.

Yes, this is how AIO works.

Is there some docs about mastercontainer development? Where is the place where the PHP code starts new containers?

The code is here: https://github.com/nextcloud/all-in-one/tree/main/php#php-docker-controller. There you can also find some info on how to run this from source.

I would like to enhance the AIO compatibility with podman.

However, one of the main problems with podman currently is, that the included watchtower container which updates the mastercontainer is not compatible with podman. So this is one of the things that would need to be fixed. See containrrr/watchtower#1060.

And even after fixing this, I am personally against adding support for podman, since, as stated in the docs, this would add another platform that we would need to test against. So you still have the option to either use docker rootless, use the manual-install https://github.com/nextcloud/all-in-one/tree/main/manual-install or follow #3487 which is not supported by us though.

[aanno]

Dear @szaimen ,

thank you for prompt answer. I completely understand that there a no plans to get podman official supported. However, I really think that AIO is just very near to unofficially run on podman right now.

Podman has evolved substantially over the years. And it certainly supports the docker engine API out of the box, even in rootless mode. The following lines start the socket:

# start socket in rootless mode
systemctl --user restart podman.socket
# check if socket is up
curl -H "Content-Type: application/json" \
        --unix-socket /run/user/$UID/podman/podman.sock \
    http://localhost/_ping
export DOCKER_SOCKET=/run/user/$UID/podman/podman.sock
export DOCKER_HOST=unix://$DOCKER_SOCKET
echo "export DOCKER_SOCKET=$DOCKER_SOCKET"
echo "export DOCKER_HOST=$DOCKER_HOST"

The socket is not at /var/run/docker.sock. But apart from that it is up and kicking. In my experiments the watchtower container has not been a problem.

However 'self reference' is still a bit difficult.