Cloning sites stopped working

Support
1

Local seems to have lost the ability to clone sites.

Whichever site I’m trying to clone, local just shows “Adding site - Creating site container from clone” but apparently fails to do anything at all.

If I quit and then restart local after having looked at this dialog for about half an hour or so, the cloned directory containing all the ~/app/public/ and ~/app/sql stuff (i.e. wordpress and its contents) are not created, and local quite rightly as well as rather unsurprisingly tells me “Missing Hosts Entry” and “WordPress does not exist in this site’s public directory”; starting the site gives a “Error response from daemon: No such container: null”.

It does not matter if the site I try to clone is a new, blank WP install or some client site filled with content; it also does not make a difference if its using Apache or NGiNX.

Local Log is saying
> warn: [main/index] Unhandled Rejection at: Promise Promise {

  <rejected> TypeError: site[f48][n48] is not a function
    at v70 (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/actions-sites/cloneSite.js:1:5893)
    at process._tickCallback (internal/process/next_tick.js:103:7) }  reason:  TypeError: site[f48][n48] is not a function
    at v70 (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/main/actions-sites/cloneSite.js:1:5893)
    at process._tickCallback (internal/process/next_tick.js:103:7)
1 Like
2

same here!

3

@philipcreativz ,

Are you on macOS or Windows?

@philby, are you still having this issue with 2.0.3?

4

Just came here to tell @philipcreativz that cloning works using 2.0.3.
I guess this might have been a case of “no space left on the virtualbox disk”

1 Like
5

Cloning does not work for me either (2.0.6). However, cloning a newly created test site works, but not certain “established” ones. Sad, since we need a working setup in our team.

Clueless.

6

Hm, just tested here. Cloning seems to work (2.0.6) for old sites.
On first start of a cloned local site, I have to change the webserver from NGiNX to Apache and back, but then things seem OK so far.
For some reason Local seems to keep track of where a site was cloned from:
“clonedImage”: [
“sha256:f5d2bc645a1f9d0c9fb8efbb1(…)”,
“sha256:d6fac44b58a8e9bf2b0d287c(…)”,
“sha256:4a7dc87b0bae989efab11839(…)”

@pose Maybe the way @scottclark handles Local for more than one dev setups could help you?

7

Hi @philby

Thank you for your answer, much appreciated :slight_smile: However, I think that the whole idea behind Local is that it should be easy to use and work straight out of the box. When I need to try different workarounds and hacks in order to get it working, I lose my patience. I’m done working for free as a beta testers for companies not doing their job. Of course; no offence to you – and, actually no offence to FlyWheel either. It’s just the way it is.

Going to try “vanilla” Docker instead.

8

Hi @pose,

I apologize for the trouble!

We do a large amount of internal testing before any release and we haven’t seen this issue recently.

If you don’t mind, can you try cloning the site again and then share the log file? You can find it by going to Help » Reveal Local’s log.