arcan1s/ahriman

Docker Container

Closed this issue · 5 comments

Feature summary

Create a Docker container

Cause of the feature request

Unable to install and use ahriman after multiple attempts while following documentation would like to just use a Docker container that just works™

Proposed changes and/or features

Create a Docker container so for ease of installation

whereas it will still require some manual things (like passing repository name or passing directories inside containers), I like this idea so I will check what is the best way to pack the application into container

Hey there!

I've added docker image which can be found at https://hub.docker.com/r/arcan1s/ahriman. Currently there is only latest image which is built against current master (thus the full name is arcan1s/ahriman:latest), but later I will create also tags for the specific package versions.

I've tested basic functionality like web interface, package building and updating process with vanilla configuration (no reports, no sync, no auth), but other features should work more or less.

More detailed description (including available environment variables) can be found at faq.

Awesome! I'll get to trying the Docker image on my server. Thank you.

some fixes have been added with the latest commits:

  • fed2f3a: rename tags according to convention, current master builds will be named as edge, latest tag will point to the latest released version. Images for specific tags will be also available starting from the next release
  • 28cc38a: one more variable for host address, database support, better unsafe command definition (previous version sometimes had errors with parsing commands, e.g. empty command or command which starts with -
  • massive changes with repository initialization in 1312129 - technically changes are not for docker itself, but it has been found by image testing that in some cases there are issues with file permissions and configuration due to split init and setup subcommands
  • 06ec16a: small addition of user support, though improvements from #55 are required to work without side effects

I'm closing this issue as implemented for now. Feel free to fill new issue in case if you would find any issues