Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Apr 03 11:47
    GMTA synchronize #1306
  • Apr 03 11:43
    GMTA edited #1306
  • Apr 03 11:42
    GMTA opened #1306
  • Apr 02 18:28
    jacobsaw commented #1268
  • Apr 02 17:54
    lmakarov commented #1268
  • Apr 02 13:48
    lpeabody commented #1268
  • Apr 02 13:09
    kenrbnsn commented #1268
  • Apr 02 11:46
    GMTA commented #1302
  • Apr 02 11:42
    GMTA commented #1302
  • Apr 01 19:35
    sloped opened #1305
  • Apr 01 09:26
    ms-marcus commented #1258
  • Mar 26 23:01
    jtphelan opened #1304
  • Mar 21 13:10
    achekulaev commented #1302
  • Mar 21 13:09
    achekulaev commented #1302
  • Mar 21 13:02
    achekulaev edited #1303
  • Mar 21 13:02
    achekulaev labeled #1303
  • Mar 21 13:02
    achekulaev assigned #1303
  • Mar 21 13:02
    achekulaev labeled #1303
  • Mar 21 13:02
    achekulaev opened #1303
  • Mar 21 11:27
    GMTA commented #1302
Frederick Henderson
@frederickjh
@martymcflysenior are you using Windows Build version 18917 or higher?
martymcflysenior
@martymcflysenior
I'm on WSL version 1 though....I know this based on the build number
nope....I'm not
Frederick Henderson
@frederickjh
Does Docksal work on WSL 1?
martymcflysenior
@martymcflysenior
it does with docker desktop, but it's really slow in my experience
I wonder if docksal doesn't support WSL 1 with Virtual Box?
Frederick Henderson
@frederickjh
@martymcflysenior Check out the link in the previous post by @saurabhar on Mar 23 11:19. We were trying to solve his Windows / Docksal issues.
He says there is an issue with earlier versions of Windows.
martymcflysenior
@martymcflysenior
@frederickjh , it looks like a different error but we're both on WSL 1
Frederick Henderson
@frederickjh
I not sure I can help you more maybe one of the developers can. @lmakarov @achekulaev Do you have any ideas what the issue is?
martymcflysenior
@martymcflysenior
thanks @frederickjh for all the help. I gave up on WSL version 1 and can't update my windows build so I'm trying to install my site on a Ubuntu Virtual machine with Virtualbox.
Frederick Henderson
@frederickjh
I hope that works out for you. :smile:
martymcflysenior
@martymcflysenior
on fin init, I keep seeing this though:
"Step 2 Initializing site...
Error: EACCES: permission denied, scandir '/var/www'
TypeError: Cannot read property 'get' of undefined"
I came across this: docksal/docksal#661 so in Ubuntu I tried chown 1000:1000 /root but same error persists.
Frederick Henderson
@frederickjh
@martymcflysenior Are you running as the root user then?
Worth noting, that this will only happen when running as root, which we do not recommend anyway.
martymcflysenior
@martymcflysenior
nope
Frederick Henderson
@frederickjh
In the docker host that is.
On the docker host if you run whoami what does it return?
martymcflysenior
@martymcflysenior
I'm running fin init in the shared folder which seems to be the issue since running fin init in a local folder works fine
Frederick Henderson
@frederickjh
Not in a Docksal container.
martymcflysenior
@martymcflysenior
me@me-VirtualBox: /media/sf_Sites/mysite$ whoami
me
Frederick Henderson
@frederickjh
What does id return on the docker host?
I am looking for the uid.
martymcflysenior
@martymcflysenior
How do I find the id?
Frederick Henderson
@frederickjh
Run id.
It should be at the beginning.
uid=(10000) me . . .
uid means User ID
martymcflysenior
@martymcflysenior
yeah, it's returning uid=1000(me) gid=1000(me) ...
Frederick Henderson
@frederickjh
OK, then try running this on the docker host chown 1000:1000 <docksal-project-root-directory>.
Where <docksal-project-root-directory> is a folder containing a Docksal project.
martymcflysenior
@martymcflysenior
the ownership doesn't change on the shared folder when doing chown...hmm
Frederick Henderson
@frederickjh
Try again with the recursive option: chown -R 1000:1000 <directory>.
martymcflysenior
@martymcflysenior
I get the same error even with recursive
I'll just use a local/non shared directory....thanks again @frederickjh
Frederick Henderson
@frederickjh
:thumbsup:
martymcflysenior
@martymcflysenior

Looking for any tips to resolve this error:

 Error response from daemon: driver failed programming external connectivity on endpoint docksal-vhost-proxy (486f21a98065ed362ec38a070c020cf4a8d6b284670485ec0c8cbab4d933d0f2): Error starting userland proxy: listen tcp 192.168.64.100:8443: bind: cannot assign requested address.

I've turned apache and mysql off locally. And have set the ports like so:
DOCKSAL_VHOST_PROXY_PORT_HTTP=8080
DOCKSAL_VHOST_PROXY_PORT_HTTPS=8443

Frederick Henderson
@frederickjh
@martymcflysenior this looks like an issue with one of the Docksal containers docksal-vhost-proxy. I don't have the server running right now with Docksal on it. Do a fin help and find the comand to restart the Docksal system containers.
martymcflysenior
@martymcflysenior
@frederickjh , anything else to try? I've done fin restart which results in this:
ERROR: Unable to talk to docker daemon.
Frederick Henderson
@frederickjh
What does docker ps --all return? @martymcflysenior
Try fin system restart @martymcflysenior I think the command you were trying above just restarts the project containers.
martymcflysenior
@martymcflysenior
$ fin docker ps --all
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f92121574dad docksal/vhost-proxy:1.5 "docker-entrypoint.s…" 34 seconds ago Created docksal-vhost-proxy
fin system reset throws the same error about "Failed starting the proxy service." Looking back, the install didn't go smooth. This happened at the end of the install:
mount: /c: cannot mount //192.168.64.1/docksal-c read-only.
exit status 32
Mount command failed... Trying an alternative method...
mount: /c: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program.
exit status 32
ERROR: SMB share mount failed.
Make sure your Windows password is correct and run fin vm mount to try again.
For troubleshooting instructions see https://docs.docksal.io/troubleshooting/windows-smb/
Resetting Docksal system services...
  • proxy
    C:\Users\me.docksal\bin\docker.exe: Error response from daemon: driver failed programming external connectivity on endpoint docksal-vhost-proxy (e3a4a6b96cf0f8dbcfb4e1926b552feaad5b1768c267963b98080480a90aa5d9): Error starting userland proxy: listen tcp 192.168.64.100:443: bind: cannot assign requested address.
    ERROR: Failed starting the proxy service.
Frederick Henderson
@frederickjh

Yes, that does not look correct. The mount is read only. I think you need to fix that.

Make sure your Windows password is correct and run fin vm mount to try again.

The error message has a link to troubleshooting help.
kamal2222ahmed
@kamal2222ahmed
on fin reset, i am getting error : Failed starting the proxy service.
i am on Mac OSX
Frederick Henderson
@frederickjh
Possibly Issue 5. Conflicting Ports from the Docksal Troubleshooting common issues.
martymcflysenior
@martymcflysenior
@kamal2222ahmed I resolved that error by removing all other vm's and removing virtual box, reinstalling docksal and letting the installer reinstall virtual box