[Backlogmanager] [FIWARE-JIRA] (HELP-13320) [fiware-stackoverflow] Docker compose fiware WireCloud data persistance not loaded from volume

Fernando Lopez (JIRA) jira-help-desk at jira.fiware.org
Tue Jan 16 16:41:00 CET 2018


     [ https://jira.fiware.org/browse/HELP-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez reassigned HELP-13320:
-------------------------------------

    Assignee: Álvaro Arranz

> [fiware-stackoverflow] Docker compose fiware WireCloud data persistance not loaded from volume
> ----------------------------------------------------------------------------------------------
>
>                 Key: HELP-13320
>                 URL: https://jira.fiware.org/browse/HELP-13320
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Álvaro Arranz
>              Labels: docker-compose, fiware, fiware-wirecloud, postgresql
>
> Created question in FIWARE Q/A platform on 11-12-2017 at 09:12
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/47748639/docker-compose-fiware-wirecloud-data-persistance-not-loaded-from-volume
> +Question:+
> Docker compose fiware WireCloud data persistance not loaded from volume
> +Description:+
> I am using a docker container for my FiWare WireCloud. It is working properly but when I stop my container with docker compose down and restart it with docker compose up all my data are erased even if I specified a volume for the postgresql database and I have the following error:
> ERROR:  relation "wirecloud_workspace" does not exist at character 370
> If I want to make it work again, I have to recreate the whole database from scratch (initdb & createsuperuser)
> What I would like to do is to be able to save my wirecloud data inside a volume and be able te backup it and reload it. Here is my current docker-compose.yml file in version 3:
> version: '3.3'
> services:
>     iot-mongo:
>         image: mongo:3.2
>         ports:
>          - "27017:27017"
>         volumes:
>             - ./data/mongo:/data/db
>     orion:
>       image: fiware/orion:1.9.0
>       links:
>         - iot-mongo
>       ports:
>         - "1026:1026"
>       command: -dbhost iot-mongo
>     nginx:
>         restart: always
>         image: nginx:1.13
>         ports:
>             - "80:80"
>             - "443:443"
>         volumes:
>             - ./nginx/nginx.conf:/etc/nginx/nginx.conf:ro
>             - ./nginx/sites-available:/etc/nginx/sites-available
>             - ./letsencrypt/well-known:/www/letsencrypt
>             - /etc/letsencrypt/:/etc/letsencrypt/
>             - wirecloudwww:/var/www/static
>             - wirecloudinstance:/opt/wirecloud_instance
>         links:
>             - wirecloud:wirecloud
>             - orion:orion
>     postgres:
>         restart: always
>         image: postgres:latest
>         ports:
>             - "5432:5432"
>         volumes:
>             - postgresdata:/var/lib/postgresql
>         environment:
>             POSTGRES_USER: postgres
>             POSTGRES_PASSWORD:
>             POSTGRES_DB: postgres
>             PGDATA: /tmp
>     wirecloud:
>         restart: always
>         image: fiware/wirecloud:1.0-composable
>         links:
>             - postgres:postgres
>         volumes:
>             - wirecloudwww:/var/www/static
>             - wirecloudinstance:/opt/wirecloud_instance
>     volumes:
>         wirecloudwww: {}
>         wirecloudinstance: {}
>         postgresdata: {}
> I also tried with docker-compose v1 like they show in the documentation but the result is the same.



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)


More information about the Backlogmanager mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy