New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ddev is not mounting sites/default/files into the web container #6026
Comments
I thought the flag was ddev import-files --source=/path/to/files.tar.gz |
Apologies it is |
Hi @cstuart, please provide the output for I assume you are using macOS, and this has something to do with Mutagen. |
Let us know when you've updated this and we'll be happy to help, but we need more information. We're happy to help in #support in Discord too, https://discord.gg/5wjP76mBJD |
FYI, As far as how they end up inside the container: On a normal Drupal project they will be bind-mounted by Docker into the container. |
@cstuart you say
But they would not be in /web. The assets will be in /var/www/html/web/sites/default/files If you see them in your project's web/sites/default/files folder and you do not see them in /var/www/html/web/sites/default/files then please show the output of this:
And please attach a file with If you have edited the .ddev/mutagen/mutagen.yml file, please remove that file and |
BTW, per your description, this has nothing to do with |
@rfay I've updated the Steps to reproduce to make it as explicit as I can. |
Just so you know, when you
|
Here's an idea for you.
|
This sounds like an issue we are experiencing as well. Does
You can get the same result if you delete the web/sites/default/files directory manually on the host and then recreate it with different contents. If I run |
It deletes the contents of web/sites/default/files @richardbporter I think it would be best for you to open a new issue and please do the requested And if you could try the suggestions in #6026 (comment) first, that would be great. |
Or if you want to save yourself the hassle you can use |
Agreed, there is nothing all that magical about |
That is essentially the workaround we are going to take for our provider import_files functionality, which is where our team is running into this. I'll create that other issue though when I can. |
Is there an existing issue for this?
Output of
ddev debug test
Expand `ddev debug test` diagnostic information
Expected Behavior
Expected the
ddev import-files
command to mount the files to the container as they are not accessible unless the container gets restarted.Actual Behavior
Files are not being mounted to container.
Steps To Reproduce
ddev start
touch web/sites/default/files/junk.txt
ls -l web/sites/default/files
ddev exec ls -l web/sites/default/files
ddev import-files --source=latest.files.tar.gz
ls -l web/sites/default/files
touch web/sites/default/files/junk.txt
ls -l web/sites/default/files
ddev exec ls -l web/sites/default/files
The text was updated successfully, but these errors were encountered: