Connect to preexisting mariaDB Docker container #143
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#143
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
I am trying to host Vikunja but there is something that I am missing: from the full instructions it seems like I need to run a specific db container for mariaDB but I already have an existing one hwere I handle all my databases.
What would be the right way to make sure Vilkunja connects to that container (I am using docker-compose)?
The usual way of running this with docker compose would be to have a seperate database container just for Vikunja, in the same docker compose configuration.
Is your mysql running on the docker host? Then you should be able to communicate from inside the docker container by using the host ip as db host - take a look at this stackoverflow question about how to achieve this.
If you run the database in a docker container somewhere, you will need to put the database and Vikunja container in the same docker network. Take a look at the docker-compose docs about that.
Again, usually you just run a db container along with the app container.
Closing this due to inactivity - feel free to repoen.