Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Mar 03 21:07
    yurg closed #1468
  • Mar 03 16:36
    yurg opened #1468
  • Mar 02 20:48
    lmakarov edited #1421
  • Mar 02 20:47
    lmakarov edited #1421
  • Mar 02 16:29
    lmakarov edited #1421
  • Mar 02 16:28
    lmakarov commented #1421
  • Mar 01 15:42
    lmakarov unlabeled #1296
  • Feb 25 19:02
    wantell commented #1404
  • Feb 24 20:22
    lmakarov edited #1215
  • Feb 24 20:21
    lmakarov commented #1215
  • Feb 24 19:10
    gconry18 commented #1055
  • Feb 24 07:24
    alanmels closed #1467
  • Feb 24 07:24
    alanmels commented #1467
  • Feb 24 03:17
    alanmels commented #1467
  • Feb 24 03:14
    alanmels commented #1467
  • Feb 24 03:12
    alanmels edited #1467
  • Feb 24 03:11
    alanmels edited #1467
  • Feb 24 03:07
    alanmels opened #1467
  • Feb 20 00:27
    shelane synchronize #1463
  • Feb 17 17:28
    lmakarov closed #1466
Leonid Makarov
@lmakarov

I have a question regarding solr

@MichielHuijse Unfortunately, our Solr docs are not up-to-date for the current Search API module versions. The setup is difficult to automate as Solr configs now have to be generated by your Drupal site.
Feel free to chime in here - docksal/docksal#1152

I am conducting a panel about local development environments at Drupalcon Europe and we lost communication. Drupalcon is next week so we are a little worried...

@ricardoamaro I'm going to PM you

wah22
@wah22

I have a D9 install with Docksal that will run behat, but I get this error:

    Element not found with xpath, //html
           (WebDriver\Exception\NoSuchElement)

I suspect it has to do with my behat configs.

I have done some research online with the error message and there were suggestions to do things like add this to my tests/behat/behat.yml file

        capabilities:
          browser: "chrome"
          version: "*"
          extra_capabilities:
            chromeOptions:
              w3c: false

But this didn't seem to work. I also added this to my docksal.yml file

      browser:
        hostname: browser
        # Pin selenium image to an older version
        # See https://github.com/docksal/docksal/issues/1096#issuecomment-543316840
        image: selenium/standalone-chrome-debug:3.141.59-oxygen
        dns:
          - ${DOCKSAL_DNS1}
          - ${DOCKSAL_DNS2}

I can see online that I should look at the D7 advanced boilerplate code for examples, but I am not sure which part of it is outdated.

What parts of https://github.com/docksal/boilerplate-drupal7-advanced behat configs do I need to change if I am running Drupal 9?

Here is my behat.yml file: ( I am assuming that the base_url is the url I use in my browser when I look at the page )

    default:
      autoload:
        '': '%paths.base%/tests/behat/features/bootstrap'
      suites:
        default:
          contexts:
            - Drupal\FeatureContext
            - Drupal\DrupalExtension\Context\DrupalContext
            - Drupal\DrupalExtension\Context\MinkContext
            - Drupal\DrupalExtension\Context\MessageContext
            - Drupal\DrupalExtension\Context\DrushContext
          paths:
            features: '%paths.base%/tests/behat/features'
      extensions:
        Behat\MinkExtension:
          default_session: 'selenium2'
          goutte: ~
          selenium2: ~
          base_url: 'http://myprojectname.docksal'
        Drupal\DrupalExtension:
          blackbox: ~
          api_driver: 'drupal'
          drush:
            alias: 'local'
          drupal:
            drupal_root: '%paths.base%/docroot'

Here is my tests/behat/behat.yml file:

    # Docker profile.
    # For use inside the CLI container in Docksal.
    docker:
      extensions:
        Behat\MinkExtension:
          # URL of the site when accessed inside Docksal.
          base_url: http://myprojectname.docksal
          # Configure browser to be used. Browser must be available on wd_host.
          # Stick with chrome by default. It's 2x faster than firefox or phantomjs (your results may vary).
          browser_name: chrome
          selenium2:
            wd_host: http://browser:4444/wd/hub
            capabilities:
              browser: "chrome"
              version: "*"
              extra_capabilities:
                chromeOptions:
                  w3c: false
        Drupal\DrupalExtension:
          drupal:
            # Site docroot inside Docksal.
            drupal_root: /var/www/docroot
          drush:
            # Site docroot inside Docksal.
            root: /var/www/docroot

This is my docksal.yml file:

    version: "2.1"
    services:
      # Web
      web:
        extends:
          file: ${HOME}/.docksal/stacks/services.yml
          service: apache
        depends_on:
          - cli

      # DB
      db:
        extends:
          file: ${HOME}/.docksal/stacks/services.yml
          service: mysql

      # CLI
      cli:
        extends:
          file: ${HOME}/.docksal/stacks/services.yml
          service: cli

      # Browser
      browser:
        hostname: browser
        # Pin selenium image to an older version
        # See https://github.com/docksal/docksal/issues/1096#issuecomment-543316840
        image: selenium/standalone-chrome-debug:3.141.59-oxygen
        dns:
          - ${DOCKSAL_DNS1}
          - ${DOCKSAL_DNS2}
Leonid Makarov
@lmakarov

@wah22 I've looked into the Element not found with xpath, //html issue in docksal/behat and I get the javascript tests (using selenium/standalone-chrome-debug:3.141.59-oxygen) passing in Docker Desktop on my Mac. However, the same setup fails in CI with Travis (Ubuntu 20.04), which is very much unexpected...

What OS are you on?

wah22
@wah22
@lmakarov I'm on mac OS. I'm using virtual box if that helps.
wah22
@wah22
Im only using virtual box in place of docker desktop.
Leonid Makarov
@lmakarov
@wah22 testing this in a Linux VM uncovered that Element not found with xpath, //html means that Selenium was not ready to accept connections from Behat. When you give Selenium container a few seconds to initialize, the error goes away. I updated the docksal/behat repo and image
wah22
@wah22
@lmakarov Thanks!
Andy Dempster
@BrizzleRocker
Big jump for Docker today - 3.0.0!
Andy Dempster
@BrizzleRocker
Do not upgrade though...!
TimmBoeken
@TimmBoeken
Hi, I'm trying to get some WordPress installations running in Docksal Mac VM. It's working fine whether I use the WP boilerplate or install WP manually. I wanted to switch to HTTPS with fin mkcert create. The webserver works with the URL https://wptest.docksal. However when I replace the URL in the WP database with the new https, I get a «too many redirects» error in the browser. If I use a blank fin init project, followed by fin mkcert create and then try to install a freshly downloaded WP 5.6 through https://wptest.docksal/wp-admin/install.php, the styles and scripts will not load and I get a «mixed content» warning since they are linked in the HTML with the http://wptest.docksal/… URL. I never experienced something like that on any other Apache environment. Any help would be appreciated!
Leonid Makarov
@lmakarov

@TimmBoeken Docksal uses a reverse proxy, which terminates HTTPS connections and passes the connection on to the apps as plain HTTP. In such setup, WordPress does not know when it's loaded over HTTPS, so you have to teach it.

Add the following to the top of your wp-config.php:

// Set site URL (or update this in Settings/General in admin UI)
// define( 'WP_HOME', 'https://wordpress.docksal.site/' );
// define( 'WP_SITEURL', 'https://wordpress.docksal.site/' );
// Pass "https" protocol from reverse proxies
if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') {
  $_SERVER['HTTPS'] = 'on';
}
TimmBoeken
@TimmBoeken
@lmakarov Awesome, thank you!
gabkdlly
@gabkdlly
I have run the install script several times, once as root, and I seem to have put my installation in a bad state ( running fin update fails with Docker installation/upgrade has failed. ). I have followed the instructions to remove the installation, but that throws errors too ( docker-compose executable was not found. (Try running 'fin update') )
gabkdlly
@gabkdlly
Ah, it seems I had a bad GPG key hanging around in the apt configuration. Seems solved now.
I looked at the code for fin, and I am guessing that fin aborted the update because the addition of the docker GPG key returned an error.
Leonid Makarov
@lmakarov

Ah, it seems I had a bad GPG key hanging around in the apt configuration. Seems solved now.

@gabkdlly glad you were able to solve the issue and thanks for sharing the details here

MatteoBorgognoni
@MatteoBorgognoni
Hi, I am trying to connect 2 different applications deployed on 2 separate docksal stacks. I have an API deployed on abc.docksal and a website deployed on xyz.docksal but all requests fail with curl: (6) Could not resolve host. I have tried to find a solution online but I can't really figure this out. Can please anybody help?
Leonid Makarov
@lmakarov

@MatteoBorgognoni Try https://docs.docksal.io/stack/configuration-variables/#docksal-dns-disabled
This will switch your local Docksal instance over to using the publicly resolvable docksal.site base domain. You would then access your stacks as abc.docksal.site and xyz.docksal.site. This is bulletproof and will always work.

We will eventually switch over to the public .docksal.site base domain and retire .docksal.

If that does not seem like a good option, then file an issues on Github including the diagnostics information.

MatteoBorgognoni
@MatteoBorgognoni
Thanks @lmakarov I can now successfully ping the two stacks successfully but I'm now having Curl timeout issues: cURL error 7: Failed to connect to xyz.docksal.site port 443: Connection timed out
Leonid Makarov
@lmakarov
@MatteoBorgognoni ok, please head over to https://github.com/docksal/docksal/discussions and create a new thread there. Include the output from fin sysinfo and then fin config for each of your stacks.
MatteoBorgognoni
@MatteoBorgognoni
Hi @lmakarov I've created an issue with the config info docksal/docksal#1460
jkeasley
@jkeasley
Hi, having an issue with a docksal drupal instance, running under wsl on win 10, no project files are mounted in thei containers?
running docker desktop 2.1.0.5 (newer won't create the containers at all) and ubuntu 20.04
Ivan Berezhnov
@ivan-berezhnov
Hi, everyone
Can you please help me
I have install the Docksal as a server on AWS for small internal project
but I need add ssl keys (certs). I read instruction and have tried but had fail
maybe someone has experience with it
Alan Mels
@alanmels
Hi guys. Can't get Docksal running on Ubuntu 20.4
It's giving:
Checking connectivity to http://dns-test.docksal... Host: FAIL
Debug info:
----------
+ cat /etc/resolv.conf
+ grep 192.168.64.100
+ ping -c 1 -W 1 dns-test.docksal
ping: dns-test.docksal: Name or service not known
+ nslookup -timeout=1 dns-test.docksal 192.168.64.100
Server:        192.168.64.100
Address:    192.168.64.100#53

Name:    dns-test.docksal
Address: 192.168.64.100Debug info:
----------
+ cat /etc/resolv.conf
+ grep 192.168.64.100
+ ping -c 1 -W 1 dns-test.docksal
ping: dns-test.docksal: Name or service not known
+ nslookup -timeout=1 dns-test.docksal 192.168.64.100
Server:        192.168.64.100
Address:    192.168.64.100#53

Name:    dns-test.docksal
Address: 192.168.64.100
Leonid Makarov
@lmakarov

Docksal as a server on AWS

@ivan-berezhnov we have an official CloudFormation template that will spin up a Docksal server on AWS with all of the bells and whistles. Take a look :)

https://github.com/docksal/sandbox-server/tree/develop/aws-cloudformation

Can't get Docksal running on Ubuntu 20.4

@alanmels I see you've already figured it out in docksal/docksal#1467. Thanks for sharing. We will prioritize switching to docksal.site in the next release.

Leonid Makarov
@lmakarov

having an issue with a docksal drupal instance, running under wsl on win 10

@jkeasley please create a ticket in Github if this is still an issue for you.

jatingarg1989
@jatingarg1989

Hi all, I am running fin init command but I was not able to create database
fin init give me error "Database Creation failed" when i tried running fin db create test it gives me error "No such container"

How can i get mysql image in docksal

jatingarg1989
@jatingarg1989
I have testing creating new project from default stack and still not able to create db
giving below error
ERROR: for db Cannot start service db: error while mounting volume '/var/lib/docker/volumes/test_project_root/_data': failed to mount local volume: mount :/Users/jatinkumar/Projects/test:/var/lib/docker/volumes/test_project_root/_data, flags: 0xc00, data: addr=192.168.64.1,vers=3,nolock,noacl,nocto,actimeo=1: permission denied
Vladimir
@itgraine
Hello guys! Tell me who had problems with user settings for memory limit? I do everything according to this instruction https://blog.docksal.io/overriding-php-settings-in-docksal-3ae246c7c588 but the dimit does not change, it always costs 256M
Leonid Makarov
@lmakarov
@itgraine that blog post is from 4 years ago. docs.docksal.io is the best first place to look for answers:
https://docs.docksal.io/service/cli/settings/#configuration
Leonid Makarov
@lmakarov

ERROR: for db Cannot start service db: error while mounting volume

@jatingarg1989 Do a fin system stop && fin system start and check the output for any errors.
Check https://docs.docksal.io/troubleshooting/common-issues for the common issues.

If nothing there helps, post your issues to https://github.com/docksal/docksal/discussions and provide the output from fin sysinfo

Leonid Makarov
@lmakarov
jatingarg1989
@jatingarg1989
@lmakarov I was able to solve the problem by doing DOCKER_VOLUME= bind instead of nfs

But after running fin init I was able to get project url in apache I see few warning because of which I was not able to load site

Configuring Apache2 environment variables...

AH00112: Warning: DocumentRoot [/var/www/docroot] does not exist

AH00112: Warning: DocumentRoot [/var/www/docroot] does not exist

[Mon Mar 01 15:54:21.570053 2021] [ssl:warn] [pid 1:tid 274908613512] AH01909: web:443:0 server certificate does NOT include an ID which matches the server name

AH00112: Warning: DocumentRoot [/var/www/docroot] does not exist

AH00112: Warning: DocumentRoot [/var/www/docroot] does not exist

[Mon Mar 01 15:54:21.621938 2021] [ssl:warn] [pid 1:tid 274908613512] AH01909: web:443:0 server certificate does NOT include an ID which matches the server name

[Mon Mar 01 15:54:21.627267 2021] [mpm_event:notice] [pid 1:tid 274908613512] AH00489: Apache/2.4.35 (Unix) LibreSSL/2.6.5 configured -- resuming normal operations

[Mon Mar 01 15:54:21.630603 2021] [core:notice] [pid 1:tid 274908613512] AH00094: Command line: '/usr/local/apache2/bin/httpd -D FOREGROUND'

jatingarg1989
@jatingarg1989

hi @lmakarov ,
few more things.

  1. I am not able to see "docksal DNS" entry there .
  2. "vhost-proxy" is starting/stoping automatically ,

is there anything specifically, we should do for these 2.

Hendrik Kuck
@uniquename
Hi, maybe I'm just overseeing something... what is the simplest way to have custom shell aliases for the cli, like "alias ll='ls -al"
Leonid Makarov
@lmakarov

@jatingarg1989

I am not able to see "docksal DNS" entry there .

You may have it configured to be disabled (https://docs.docksal.io/stack/configuration-variables/#docksal-dns-disabled).

"vhost-proxy" is starting/stoping automatically ,

?

Leonid Makarov
@lmakarov

what is the simplest way to have custom shell aliases for the cli, like "alias ll='ls -al"

@uniquename ~/.bashrc inside cli.

docker@cli:/var/www$ echo "alias hey='echo Hello World'"  >> ~/.bashrc && source ~/.bashrc
docker@cli:/var/www$ hey
Hello World

The ll alias is already there, commented out.

2 replies
jatingarg1989
@jatingarg1989

Hi @lmakarov , Yes

V-host is starting-stoping automatically.
for DNS, let me check once.

thanks for your reply !!

jatingarg1989
@jatingarg1989

Hi @lmakarov I run the command fin config set --global DOCKSAL_NO_DNS_RESOLVER=1 and then fin system reset it gives me below error

Configuring network settings...
Configuring NFS shares...
NFS shares are already configured
Resetting Docksal system services...

  • proxy
    WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
  • dns
    Password:
    Clearing DNS cache...
  • ssh-agent
    WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
    Identity added: id_rsa (jatinkumar@jatins-MacBook-Pro.local)
Leonid Makarov
@lmakarov

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

@jatingarg1989 oh boy... are you on an M1 Mac? Docksal does not yet support ARM.
Thumb up this issue to join the club docksal/docksal#1421

jatingarg1989
@jatingarg1989
@lmakarov yes it is M1 Mac :(
eslipsager
@eslipsager

I'm trying to set up an NGINX reverse proxy for a path in the site - and have it MOSTLY working. In my NGINX vhost configs I've got this:

 location /MYPROXIEDPATH {
      # access_log off;
      access_log      /var/log/nginx/access.log;
      error_log       /var/log/nginx/error.log;
      proxy_pass https://whatever.com;
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header Host $host;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

      proxy_buffering off;
      proxy_cache off;
      proxy_read_timeout 4h;
   }

and in the server section:

 server {
     listen 80 default_server;
     server_name _;
     root /var/www/build/html;
     proxy_cookie_path / "/; HTTPOnly; Secure";
     underscores_in_headers on;

It mostly appears to be working - but cookies from the proxied domain aren't being set/honored locally. I've been pulling my hair out over this for quite some time.

Is there some sort of upstream issue that I'm missing? Thanks for any kind of help!