All layout lost after docker down / up

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • FilippoLec
    Junior Member
    • Feb 2026
    • 10

    #1

    All layout lost after docker down / up

    Is there a specific reason why I lose all the layout changes if I pull the docker container of EspoCRM down and then up again?

    I tried by just changing the interface color and when performing docker compose down and then up al the canges are gone including any new entity fields, visualization layouts and basically the UI gets back to default.

    The weird thing is that the data inserted is still in the database so you would have the issue of data not being visible because there is not a field to represent it; when adding the field back the data comes back.

    Even weirder is that if I create a Layout group in the user window the group remains even with the (now) absent entity fields but without showing them.

    I don't know if this might have something to do with this issue but I see the docker espocrm-daemon and espocrm-websocket containers are constantly saying "Instance is not ready: waiting for installation".

    EspoCRM Version 9.0.8

    Docker compose:
    HTML Code:
    services:
      
      espocrm-db:
        image: mariadb:latest
        container_name: espocrm-db
        command: --max-allowed-packet=64MB
        restart: unless-stopped
        environment:
          MARIADB_ROOT_PASSWORD: [root_password]
          MARIADB_DATABASE: [espocrm]
          MARIADB_USER: [espocrm]
          MARIADB_PASSWORD: [database_password]
        volumes:
          - espocrm-db:/var/lib/mysql
        healthcheck:
          test: ["CMD", "healthcheck.sh", "--connect", "--innodb_initialized"]
          interval: 20s
          start_period: 10s
          timeout: 10s
          retries: 3
    
      espocrm:
        image: espocrm/espocrm:latest
        container_name: espocrm
        environment:
          ESPOCRM_DATABASE_HOST: [espocrm-db]
          ESPOCRM_DATABASE_USER: [espocrm]
          ESPOCRM_DATABASE_PASSWORD: [database_password]
          ESPOCRM_ADMIN_USERNAME: [root]
          ESPOCRM_ADMIN_PASSWORD: [root_password]
          ESPOCRM_SITE_URL: "https://espocrmurl.espocrm.com"
        restart: unless-stopped
        volumes:
          - espocrm:/var/www/espocrm
        depends_on:
          espocrm-db:
            condition: service_healthy
        ports:
          - 8080:80
    
      espocrm-daemon:
        image: espocrm/espocrm:latest
        container_name: espocrm-daemon
        volumes:
          - espocrm:/var/www/espocrm
        restart: unless-stopped
        entrypoint: docker-daemon.sh
    
      espocrm-websocket:
        image: espocrm/espocrm:latest
        container_name: espocrm-websocket
        environment:
          ESPOCRM_CONFIG_USE_WEB_SOCKET: "true"
          ESPOCRM_CONFIG_WEB_SOCKET_ZERO_M_Q_SUBSCRIBER_DSN: "tcp://*:7777"
          ESPOCRM_CONFIG_WEB_SOCKET_ZERO_M_Q_SUBMISSION_DSN: "tcp://espocrm-websocket:7777"
        volumes:
          - espocrm:/var/www/espocrm
        restart: unless-stopped
        entrypoint: docker-websocket.sh
        ports:
          - 8081:8080
    
    volumes:
      espocrm-db:
      espocrm:
    Last edited by FilippoLec; 02-28-2026, 10:25 PM.
  • esforim
    Active Community Member
    • Jan 2020
    • 2225

    #2
    Wow another fresh Docker user. I'm currently using the compose too. Hopefully I don't get same issue with you. Offtopic but have you migrate your data? How do you do it?

    Anyway, based on my understanding, I believe you should have Reimage, don't create another Stack.

    Comment


    • FilippoLec
      FilippoLec commented
      Editing a comment
      Yeah I not that skilled with docker. I have restored data from a backup using the procedure indicated in the official "backup and restore" guide. This issue is not dependant on that tho; I have just pulled the containers down and then up without any modification (or migration) of the data and everything is just gone.

    • victor
      victor commented
      Editing a comment
      @FilippoLec

      Try stopping the containers with:

      Code:
      sudo docker-compose down

      not just starting them with:

      Code:
       sudo docker-compose up -d

      but with:

      Code:
      sudo docker-compose up -d --build "$@"
      Last edited by victor; Today, 12:03 PM.
  • esforim
    Active Community Member
    • Jan 2020
    • 2225

    #3
    I'm currently using Portainer for my 'manager'. So everything I do is by the GUI. Still learning how do I access the Volume

    The problem with the Backup and Restore is, it seem that I have to do a download and copy/paste it over. I was hoping there is some sort of "direct SSH??? function I can use. I got full control of both database/website

    Comment

Working...