{"action":"created","issue":{"url":"https://api.github.com/repos/bitnami/bitnami-docker-moodle/issues/80","repository_url":"https://api.github.com/repos/bitnami/bitnami-docker-moodle","labels_url":"https://api.github.com/repos/bitnami/bitnami-docker-moodle/issues/80/labels{/name}","comments_url":"https://api.github.com/repos/bitnami/bitnami-docker-moodle/issues/80/comments","events_url":"https://api.github.com/repos/bitnami/bitnami-docker-moodle/issues/80/events","html_url":"https://github.com/bitnami/bitnami-docker-moodle/issues/80","id":353462903,"node_id":"MDU6SXNzdWUzNTM0NjI5MDM=","number":80,"title":"Persistence of Moodle data incomplete","user":{"login":"zimcke","id":6987999,"node_id":"MDQ6VXNlcjY5ODc5OTk=","avatar_url":"https://avatars1.githubusercontent.com/u/6987999?v=4","gravatar_id":"","url":"https://api.github.com/users/zimcke","html_url":"https://github.com/zimcke","followers_url":"https://api.github.com/users/zimcke/followers","following_url":"https://api.github.com/users/zimcke/following{/other_user}","gists_url":"https://api.github.com/users/zimcke/gists{/gist_id}","starred_url":"https://api.github.com/users/zimcke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zimcke/subscriptions","organizations_url":"https://api.github.com/users/zimcke/orgs","repos_url":"https://api.github.com/users/zimcke/repos","events_url":"https://api.github.com/users/zimcke/events{/privacy}","received_events_url":"https://api.github.com/users/zimcke/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-08-23T16:39:00Z","updated_at":"2018-08-30T08:13:05Z","closed_at":null,"author_association":"NONE","body":"<!--\r\nIf you are reporting a new issue, make sure that we do not have any duplicates\r\nalready open. You can ensure this by searching the issue list for this\r\nrepository. If there is a duplicate, please close your issue and add a comment\r\nto the existing issue instead.\r\n\r\nIf you suspect your issue is a bug, please edit your issue description to\r\ninclude the BUG REPORT INFORMATION shown below. If you fail to provide this\r\ninformation within 7 days, we cannot debug your issue and we'll close it. We\r\nwill, however, reopen it if you later provide the information.\r\n-------------------------------\r\n    BUG REPORT INFORMATION\r\n-------------------------------\r\nUse the commands below to provide key information from your environment:\r\nYou do NOT have to include this information if this is a FEATURE REQUEST\r\n-->\r\n\r\n**Description**\r\nI have the Moodle application running with persistence on a server, and it works fine. However, I am trying to set up an additional (local) Moodle application on the same machine for testing purposes. My problem is that I cannot get the Moodle data to be persisted in a similar way. More specifically the `moodle` folder doesn't persist the Moodlee core code and plugins in my volume `moodle_data`, only the `moodledata` folder is there. Hence I cannot add my plugins, theme, etc. to the local file tree. Could this be related to the fact that I already have a Moodle application running on the same machine?\r\n\r\nAnother issue is that I cannot seem to remove the volumes after deletion of the containers. Even the `docker volume prune` doesn't detect the created folders and files. I don't have sudo access to delete these folders myself.\r\n<!-- Briefly describe the problem you are having in a few paragraphs. -->\r\n\r\n**Steps to reproduce the issue:**\r\n\r\n1. I used the following commands to create the `mariadb` and `moodle` container:\r\n\r\n``` \r\ndocker run -d --name test-mariadb --net test-environment-moodle-tier \\\r\n-e MARIADB_PORT_NUMBER=3307 \\\r\n-e MARIADB_DATABASE=test-mariadb \\\r\n-e ALLOW_EMPTY_PASSWORD=yes \\\r\n-e MARIADB_USER=bn_moodle \\\r\n-v /home/code/testenvironment/mariadb_data:/bitnami \\\r\nbitnami/mariadb \r\n\r\ndocker run -d -p 18889:80 -p 18890:443 --name test-moodle --net test-environment-moodle-tier \\\r\n-e MARIADB_PORT_NUMBER=3307 \\\r\n-e ALLOW_EMPTY_PASSWORD=yes \\\r\n -e MOODLE_DATABASE_USER=bn_moodle \\\r\n -e MOODLE_DATABASE_NAME=test-mariadb \\\r\n-v /home/code/testenvironment/moodle_data:/bitnami bitnami/moodle\r\n```\r\n2. Inspect the persisted folder when Moodle is accessible from the browser `~/testenvironment/test/moodle_data/moodle$`\r\n3. Only the folder `moodledata` is visible from that path. I would expect the Moodle core to be here as well (and that's how it is with my other application)\r\n\r\n**Describe the results you received:**\r\n\r\nI cannot see the Moodle code, plugins, themes, etc. in my persisted folder. I can also not delete persisted folder after deletion of the containers with `docker volume prune`.\r\n\r\n**Describe the results you expected:**\r\n\r\nI expect to see the Moodle code, plugins, themes, etc. in my persisted folder, to be able to modify the code and add my own plugins directly to the file tree.\r\n\r\n**Additional information you deem important (e.g. issue happens only occasionally):**\r\n\r\nMy other Moodle application is being run with the following commands:\r\n\r\n``` \r\ndocker run -d --name mariadb-master --net moodle-tier \\\r\n-e MARIADB_ROOT_PASSWORD=*** \\\r\n-e MARIADB_REPLICATION_MODE=master \\\r\n-e MARIADB_REPLICATION_USER=*** \\\r\n-e MARIADB_REPLICATION_PASSWORD=*** \\\r\n-e MARIADB_USER=code \\\r\n-e MARIADB_PASSWORD=*** \\\r\n-e MARIADB_DATABASE=mariadb-master -v /export/home1/code/persistence/mariadb_data:/bitnami bitnami/mariadb\r\n\r\ndocker run -d --name mariadb-slave --link mariadb-master:master --net moodle-tier\\\r\n -e MARIADB_REPLICATION_MODE=slave \\\r\n-e MARIADB_REPLICATION_USER=*** \\\r\n-e MARIADB_REPLICATION_PASSWORD=*** \\\r\n-e MARIADB_MASTER_HOST=master \\\r\n-e MARIADB_MASTER_ROOT_PASSWORD=**** \\\r\n-v /export/home1/code/persistence/mariadb_slave_data:/bitnami bitnami/mariadb\r\n\r\ndocker run -d -p 80:80 -p 443:443 --name moodle --net moodle-tier \\\r\n-e MARIADB_PASSWORD=*** \\\r\n-e MARIADB_HOST=mariadb-master \\\r\n-v /export/home1/code/persistence/moodle_data:/bitnami bitnami/moodle\r\n```\r\n**Version**\r\n\r\n- Output of `docker version`:\r\n\r\n```\r\nClient:\r\n Version:      17.03.2-ce\r\n API version:  1.27\r\n Go version:   go1.6.2\r\n Git commit:   f5ec1e2\r\n Built:        Thu Jul  5 23:07:48 2018\r\n OS/Arch:      linux/amd64\r\n\r\nServer:\r\n Version:      17.03.2-ce\r\n API version:  1.27 (minimum version 1.12)\r\n Go version:   go1.6.2\r\n Git commit:   f5ec1e2\r\n Built:        Thu Jul  5 23:07:48 2018\r\n OS/Arch:      linux/amd64\r\n Experimental: false\r\n```\r\n\r\n- Output of `docker info`:\r\n\r\n```\r\nDocker info output:\r\nContainers: 9\r\n Running: 5\r\n Paused: 0\r\n Stopped: 4\r\nImages: 7\r\nServer Version: 17.03.2-ce\r\nStorage Driver: aufs\r\n Root Dir: /export/home1/docker/aufs\r\n Backing Filesystem: extfs\r\n Dirs: 60\r\n Dirperm1 Supported: true\r\nLogging Driver: json-file\r\nCgroup Driver: cgroupfs\r\nPlugins: \r\n Volume: local\r\n Network: bridge host macvlan null overlay\r\nSwarm: inactive\r\nRuntimes: runc\r\nDefault Runtime: runc\r\nInit Binary: docker-init\r\ncontainerd version: 4ab9917febca54791c5f071a9d1f404867857fcc\r\nrunc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe\r\ninit version: N/A (expected: 949e6facb77383876aeff8a6944dde66b3089574)\r\nSecurity Options:\r\n apparmor\r\n seccomp\r\n  Profile: default\r\nKernel Version: 4.4.0-133-generic\r\nOperating System: Ubuntu 16.04.5 LTS\r\nOSType: linux\r\nArchitecture: x86_64\r\nCPUs: 4\r\nTotal Memory: 7.682 GiB\r\nName: code\r\nID: K3KJ:6WLL:MSKD:RJEU:VZMG:WPO4:GHKV:AX47:I7XE:W4AF:BJ54:DB7I\r\nDocker Root Dir: /export/home1/docker\r\nDebug Mode (client): false\r\nDebug Mode (server): false\r\nRegistry: https://index.docker.io/v1/\r\nExperimental: false\r\nInsecure Registries:\r\n 127.0.0.0/8\r\nLive Restore Enabled: false\r\n\r\nWARNING: No swap limit support\r\n```\r\n\r\n\r\n**Additional environment details (AWS, VirtualBox, Docker for MAC, physical, etc.):**\r\n"},"comment":{"url":"https://api.github.com/repos/bitnami/bitnami-docker-moodle/issues/comments/417230568","html_url":"https://github.com/bitnami/bitnami-docker-moodle/issues/80#issuecomment-417230568","issue_url":"https://api.github.com/repos/bitnami/bitnami-docker-moodle/issues/80","id":417230568,"node_id":"MDEyOklzc3VlQ29tbWVudDQxNzIzMDU2OA==","user":{"login":"zimcke","id":6987999,"node_id":"MDQ6VXNlcjY5ODc5OTk=","avatar_url":"https://avatars1.githubusercontent.com/u/6987999?v=4","gravatar_id":"","url":"https://api.github.com/users/zimcke","html_url":"https://github.com/zimcke","followers_url":"https://api.github.com/users/zimcke/followers","following_url":"https://api.github.com/users/zimcke/following{/other_user}","gists_url":"https://api.github.com/users/zimcke/gists{/gist_id}","starred_url":"https://api.github.com/users/zimcke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zimcke/subscriptions","organizations_url":"https://api.github.com/users/zimcke/orgs","repos_url":"https://api.github.com/users/zimcke/repos","events_url":"https://api.github.com/users/zimcke/events{/privacy}","received_events_url":"https://api.github.com/users/zimcke/received_events","type":"User","site_admin":false},"created_at":"2018-08-30T08:13:05Z","updated_at":"2018-08-30T08:13:05Z","author_association":"NONE","body":"No, of course not, they don't use the same volumes. They also have different names ('moodle' and 'test-moodle'). For 'test-moodle' I can only see the 'moodledata' in my file tree when I use the command you suggested. `docker logs` gives me for both containers the right output of the Moodle containers.\r\n\r\nNow when I try to replicate my actions from before and set up a new dev container to check if the same happens, I have trouble getting the Moodle application to connect to a new database (using a different mariadb port, docker network, name and volume). Maybe it is not a good approach to run two applications on the same server?\r\n\r\n"}}
{"actor":{"display_login":"zimcke"}}