Updates are not being reflected properly

[francescou]

Updates are not being reflected properly

[francescou]

Hi, could you please provide me an example of docker-compose.yml file to reproduce the issue?

is this related to #50 ?

[centralafricabaptistcollege]

In a way the it's related, but I'm not sure if it's completely related since the issue isn't that the volumes are being mounted wrong (like #50) its just that the wrong volume information isn't being updated, if that makes sense. As a result of #50 I decided to mount just the two volumes below. However they were both showing up as mounted. I'll try your fix to #50 and report back if it solves it. Thanks for the quick response.

  nginx:
    build: ./.docker/NGINX
    image: nginx.company.org 
    container_name: company.org
    restart: always
    environment:
        - VIRTUAL_HOST=company.org
        - DB_PORT_3306_TCP_ADDR=172.17.0.1
        - DB_ENV_MYSQL_USER=user
        - DB_ENV_MYSQL_DATABASE=database
        - DB_ENV_MYSQL_PASSWORD=password
    ports:
    - 80
    volumes:
        - ./code:/var/www/html/
        - data:/var/www/data:Z```

[centralafricabaptistcollege]

So I changed it to

- ${PWD}/code:/var/www/html/ - data:/var/www/data:Z

However, even though there is nothing in the compose file saying config.php if I push up on the docker-compose gui it only creates an empty config.php directory (!) under /var/www/html. Even though there are files in /code. If I do it via the terminal it works fine. I'm just trying to figure out where it's pulling the config.php directive from since I've deleted it from the docker-compose.yml

[centralafricabaptistcollege]

So I found something very odd. I wonder if it's an issue with the volume driver or something. I logged into the docker_compose_ui container and went to the directory containing my project repo. I opened the file in vim and it was displaying properly. However, when I ran cat on the file, it was showing a very old version of the file, which corresponded to the wrong settings I was seeing. I'm not familiar to seeing this issue with other docker images, but wonder if it might be unrelated to the docker_compose_ui. You ever seen it before?

[centralafricabaptistcollege]

So, for now what I did was actually just setup the python server from your docker file on my machine and run it that way. It bypasses all the path issues and file saving problems. It also has the benefit of being significantly faster. Conceptually I actually prefer this model as I'm hoping to use this to control my server running a number of different containers. If my docker controller is hosted on docker and docker is down I won't be able to utilize it and will lose most of the benefits of it. Obviously that's an individual choice, but I think for now I will go do this path and see how it goes.

Thanks so much for the awesome project. I had ideas of building an basic app to do essentially what this done. Glad to have been able to find this.

[francescou]

I don't think I ever had this kind of issue..you can try to execute a docker-compose down to remove previous container instances.

I'm not sure if this can help you...but I always put a slash character after the directory name, e.g.:

- ${PWD}/code/:/var/www/html/ - data/:/var/www/data/

thank you for your contribution