-
-
Notifications
You must be signed in to change notification settings - Fork 610
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
Target upload_dirs
do not have any files in them inside container, when using mutagen after a ddev pull pantheon
or ddev import-files
#6188
Comments
You shouldn't need sudo anywhere here, because the directories should already be owned by you. if you can show I assume you're using a custom hosting provider, can you share it? If not, can you say which one you're using? With Drupal the default settings.ddev.php sets up Drupal so it doesn't try to constrain permissions. You left out a huge part of the I imagine the problem is that your files tarball contains files which have limited permissions. You can easily check this by untarring the tarball in another directory and taking a look at it. If you want to share the tarball with me, I can take a look as well.
|
It seems this is actually a problem with the files_pull_command: in the pantheon.yaml. So everytime I pull, the permissions are getting messed up. Not sure the right approach to fix. Adjusted the script like so, but it still does not help.
|
Please use
It looks like you're not using https://github.com/ddev/ddev/blob/master/pkg/ddevapp/dotddev_assets/providers/pantheon.yaml.example at all? |
Here is the full ddev debug |
Apologies, that was my attempt to further debug and fix the permissions issue. The code was:
|
Thanks for providing the full I happen to note that you don't seem to have run |
Go ahead and use terminus inside the container to grab the files tarball (or maybe it's already there waiting for you in .ddev/.downloads) and extract it and look at the permissions it's using. Mostly you don't want to use sudo for anything anywhere. |
If it turns out that you can share privileges on the project so I can test against it, I'm happy to do that. Normally we only have our one simple test project. Alternately, if you want to PM me the files tarball that you can download, I'll take a look at that. I certainly haven't had this problem before. |
Thanks for sending the tarball. It has almost nothing in it, so I assume the upstream project is almost empty? When I untar it everything comes out appropriately and it looks fine, and none of the directories like You're not running Do you have any trouble if you just (I don't think I've gotten you to show the output of |
Yes upstream project is almost empty. This error happens with all of the websites big and small.
My user that I run ddev with is tesliker I will try --skip-files next |
If I skip the files, Drupal does not throw the mkdir errors |
And if you just (Is there any chance you have a Does this problem go away if you |
What does |
Maybe you should just make an appointment and we'll look at it together with a screenshare. https://cal.com/randyfay/30min |
@rfay It does look like the problem went away once I turned off performance-mode. I performed I wanted to turn it back on to see if the issue happened again, but when I ran
|
I'm sure you knew that you had to My bet is if you did this a few times in a row it might be intermittent. Someone else did have trouble with Orbstack and this situation recently, but has been impossible to sort out and unpredictable. I imagine it would be intermittent for you here as well. Tomorrow we'll have DDEV v1.23.1, which has slightly better error reporting in situations like what you may have, so if you're able to reproduce the "nothing found in .downloads" with DDEV v1.23.1, details about it will be so very welcome. That problem (related to what you just saw, but not related to your original problem) is a long thread in Discord: https://discord.com/channels/664580571770388500/1232668554550186024 |
Since your upstream project is so very limited, is there any possibility you could give me access to it so I could try to recreate? Also, you say |
@tesliker - I was just debugging an unrelated item and wanted to ask if you're running PhpStorm with the DDEV Plugin going. It could affect the intermittent behavior you just had. |
ddev pull pantheon
Tommy and I studied this pretty carefully (thanks!) and what we found was this:
I'm able to reproduce this with our test pantheon project on Orbstack 1.5.1 also (arm64 mac). In my case, I just didn't have any twig action happening, so had never seen the problem. Our tests on macOS + OrbStack really should be showing this behavior (TestPantheonPull should see this problem. Apparently it doesn't) We have OrbStack 1.5.0 on tb-macos-arm64-5 and tb-macos-arm64-6, but 1.5.1 on tb-macos-arm64-7. However, we don't do a |
This is a bug in DDEV, at least with Drupal, possibly with other CMSs. It does not have to do with Orbstack (easy to recreate with Docker Desktop). Here's the location of the failure: Lines 575 to 580 in e694c20
What's happening is the drupalImportFilesAction() is removing the entire mounted path (sites/default/files) on the host side. But when mutagen is enabled, that is the source for the in-container files directory, and when we delete and create a new one, the old one is no longer mounted. The correct behavior here will be to purge the target files directory, rather than removing it. |
ddev pull pantheon
upload_dirs
do not have any files in it inside container, when using mutagen after a ddev pull pantheon
or ddev import-files
upload_dirs
do not have any files in it inside container, when using mutagen after a ddev pull pantheon
or ddev import-files
upload_dirs
do not have any files in them inside container, when using mutagen after a ddev pull pantheon
or ddev import-files
@tesliker could you please take a look at the artifacts in #6199 (comment) and see if they solve your problem? You'll want the macOS-amd64 one, and you need to put it in your PATH in a place before /usr/local/bin in your case, or run it explicitly. In your situation I often put it in ~/bin and make sure ~/bin is first in PATH. |
@rfay Confirmed, this works. Great job, thanks! |
Thanks for taking the time to work through this! This will be in the next release of DDEV, but of course you can use the HEAD version when this gets pulled or you also have other workarounds. |
Preliminary checklist
ddev debug test
to include output belowOutput of
ddev debug test
Expand `ddev debug test` diagnostic information
Expected Behavior
Run:
The website should be available at *.ddev.site with no errors
Actual Behavior
When I initialize a new project, I have this error:
My sites/default/files folder is empty.
Once I run
sudo chmod -R 777 .
and restart the containers, the error goes away.If I run
sudo chmod -R 777 .
before creating the project, I still get the errors and have to run it again and restart.It is just weird that I have to do this for every project the first time. Not sure What I am doing wrong.
Steps To Reproduce
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: