docker container / installation log for debian
I've just spent couple evenings compiling a recipe for agendav docker image, available here It's useful as is, but also can be used as an installation log, if you look at the Dockerfile - applicable to debian/ubuntu
I am trying to configure this to run together with a docker instance of radicale on a single machine. The radicale docker runs (I can see it on localhost:5232 and login), but how do I run this docker to connect to that?
What I've done:
podman run -d --name radicale -p 5232:5232 tomsquest/docker-radicale
podman run --name agendav -p 5233:80 -e AGENDAV_CALDAV_SERVER="http://127.0.0.1:5232/" -e AGENDAV_SERVER_NAME="127.0.0.1" -e AGENDAV_LOG_DIR="/tmp/" nagimov/agendav-docker
Output:
Stopping MariaDB database server: mysqld.
Starting MariaDB database server: mysqld ..
Start webserver
/usr/sbin/apache2ctl: 99: ulimit: error setting limit (Operation not permitted)
Setting ulimit failed. See README.Debian for more information.
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.0.2.100. Set the 'ServerName' directive globally to suppress this message
root@4554ab8c3108:/tmp# cat 2019-08-13.log
[2019-08-13 14:12:29] agendav.INFO: Matched route "calendar". {"route_parameters":{"_controller":"[object] (Closure: {})","_route":"calendar"},"request_uri":"http://localhost:5233/"} []
[2019-08-13 14:12:30] agendav.INFO: Matched route "login". {"route_parameters":{"_controller":"\\AgenDAV\\Controller\\Authentication::loginAction","_route":"login"},"request_uri":"http://localhost:5233/login"} []
[2019-08-13 14:12:42] agendav.INFO: Matched route "POST_login". {"route_parameters":{"_controller":"\\AgenDAV\\Controller\\Authentication::loginAction","_route":"POST_login"},"request_uri":"http://localhost:5233/login"} []
[2019-08-13 14:12:42] agendav.CRITICAL: AgenDAV\Exception\ConnectionProblem: Error creating resource: [message] fopen(http://127.0.0.1:5232/): failed to open stream: Connection refused [file] /var/www/agendav/web/vendor/guzzlehttp/guzzle/src/Handler/StreamHandler.php [line] 312 (uncaught exception) at /var/www/agendav/web/src/Http/Client.php line 184 {"exception":"[object] (AgenDAV\\Exception\\ConnectionProblem(code: 0): Error creating resource: [message] fopen(http://127.0.0.1:5232/): failed to open stream: Connection refused\n[file] /var/www/agendav/web/vendor/guzzlehttp/guzzle/src/Handler/StreamHandler.php\n[line] 312 at /var/www/agendav/web/src/Http/Client.php:184)"} []
[2019-08-13 14:13:51] agendav.INFO: Matched route "POST_login". {"route_parameters":{"_controller":"\\AgenDAV\\Controller\\Authentication::loginAction","_route":"POST_login"},"request_uri":"http://localhost:5233/login"} []
[2019-08-13 14:13:51] agendav.CRITICAL: AgenDAV\Exception\ConnectionProblem: Error creating resource: [message] fopen(http://127.0.0.1:5232/): failed to open stream: Connection refused [file] /var/www/agendav/web/vendor/guzzlehttp/guzzle/src/Handler/StreamHandler.php [line] 312 (uncaught exception) at /var/www/agendav/web/src/Http/Client.php line 184 {"exception":"[object] (AgenDAV\\Exception\\ConnectionProblem(code: 0): Error creating resource: [message] fopen(http://127.0.0.1:5232/): failed to open stream: Connection refused\n[file] /var/www/agendav/web/vendor/guzzlehttp/guzzle/src/Handler/StreamHandler.php\n[line] 312 at /var/www/agendav/web/src/Http/Client.php:184)"} []
Many clients do not support the creation of new calendars and address books. You can use Radicale’s web interface (e.g. http://localhost:5232) to create and manage collections. In some clients you can just enter the URL of the Radicale server (e.g. http://localhost:5232) and your user name. In others, you have to enter the URL of the collection directly (e.g. http://localhost:5232/user/calendar).
see more at https://radicale.org/clients/
I've made it work thanks to using the --network="host" option in the 2nd podman run command. It would be cleaner by using a docker-compose file, but for now it works.
Would be good to add a link to the image in the docs.
@pixelbrackets thanks for cleaning things up! :+1:
#287 updates readme with a link to docker hub. Docker image is just updated to latest debian.
Is 2.4.0 stable enough to point the latest docker tag to it?
discussion in PR #287
Resolved in PR #287, a link to the image is now included in the README. Thanks for your work on this! :100: :medal_sports: