Add support for ARM64

[szaimen]

• Enable repo syncing #147
• update channel and publish logic for building containers for multiple architectures #148
• Build containers for multiple architectures: done with build images with github workflows nextcloud-releases/all-in-one#3
• fix containers for arm64 (at least in those places, maybe more: https://github.com/nextcloud/all-in-one/search?q=amd64 and https://github.com/nextcloud-releases/all-in-one/runs/4860610776?check_suite_focus=true) fixed with fix containers for arm64 #153
• fix notify push Correctly set CPU_ARCH for notify_push #162
• set up an arm64 testing machine
• test that everything works
• publish to latest
• add docs

[szaimen]

Hi there 👋,

we now build containers for arm64, too. If you have a board with an arm64 OS, you should be able to test this now using this command:

# Install docker
curl -fsSL get.docker.com | sudo sh

# Run the container
sudo docker run -it \
--name nextcloud-aio-mastercontainer \
--restart always \
-p 80:80 \
-p 8080:8080 \
-p 8443:8443 \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
nextcloud/all-in-one:develop-arm64

It wasn't tested yet but in theory everything should work out of the box. Please report back if there are issues or if everything works. Thank you! :)

[szaimen]

Fatal error: Uncaught GuzzleHttp\Exception\ClientException: Client error: POST http://localhost/v1.41/networks/create resulted in a 409 Conflict response: {"message":"network with name nextcloud-aio already exists"}

Hello, Thanks for your report! This should be fixed with #159.
Please try again by pulling the latest image (sudo docker pull nextcloud/all-in-one:develop-arm64) and running the command above again! :)

[MariusQuabeck]

Just tested this on my RPi 4, runs as expected!

[szaimen]

Hi there 👋

I just published the containers from develop-arm64 to latest-arm64!

You can switch to the new channel without data-loss by running:

# Stop current mastercontainer
sudo docker stop nextcloud-aio-mastercontainer

# Delete current mastercontainer
sudo docker rm nexcloud-aio-mastercontainer

# Recreate mastercontainer with latest-arm64 channel
sudo docker run -it \
--name nextcloud-aio-mastercontainer \
--restart always \
-p 80:80 \
-p 8080:8080 \
-p 8443:8443 \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
nextcloud/all-in-one:latest-arm64

[mrtnd]

Hi i know that the issue is closed but just wanted to ask one Question. Can i avoid the step where i need to type in a DOMAIN. I just want to use the server locally and don't need anything but the IP? Is that possible? I tried to access the server using the following:
https://IP:PORT/settings/admin/overview
but i get the this Error:

Fatal error: Uncaught Slim\Exception\HttpNotFoundException: Not found. in /var/www/docker-aio/php/vendor/slim/slim/Slim/Middleware/RoutingMiddleware.php:91 Stack trace: #0 /var/www/docker-aio/php/vendor/slim/slim/Slim/Routing/RouteRunner.php(72): Slim\Middleware\RoutingMiddleware->performRouting(Object(GuzzleHttp\Psr7\ServerRequest)) #1 /var/www/docker-aio/php/vendor/slim/csrf/src/Guard.php(456): Slim\Routing\RouteRunner->handle(Object(GuzzleHttp\Psr7\ServerRequest)) #2 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(209): Slim\Csrf\Guard->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Slim\Routing\RouteRunner)) #3 /var/www/docker-aio/php/vendor/slim/twig-view/src/TwigMiddleware.php(115): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest)) #4 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(147): Slim\Views\TwigMiddleware->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous)) #5 /var/www/docker-aio/php/src/Middleware/AuthMiddleware.php(38): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest)) #6 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(313): AIO\Middleware\AuthMiddleware->__invoke(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous)) #7 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(81): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest)) #8 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(215): Slim\MiddlewareDispatcher->handle(Object(GuzzleHttp\Psr7\ServerRequest)) #9 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(199): Slim\App->handle(Object(GuzzleHttp\Psr7\ServerRequest)) #10 /var/www/docker-aio/php/public/index.php(144): Slim\App->run() #11 {main} thrown in /var/www/docker-aio/php/vendor/slim/slim/Slim/Middleware/RoutingMiddleware.php on line 91

Am i doing something wrong?

[szaimen]

hello, running aio without a domain is not supported.

[mrtnd]

hello, running aio without a domain is not supported.

Good to know. Is that going to be supported some time in the future?

[szaimen]

Good to know. Is that going to be supported some time in the future?

No. The closest you will get is being able to use your own reverse proxy but you will need a domain in that case too.

[mrtnd]

All right. Thanks again for the quick reply.