Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 04 23:56
    lmakarov commented #201
  • Dec 04 19:06
    lmakarov review_requested #1442
  • Dec 04 19:06
    lmakarov review_requested #1442
  • Dec 04 19:06
    lmakarov review_requested #1442
  • Dec 04 19:06
    lmakarov review_requested #1442
  • Dec 04 19:06
    lmakarov labeled #1442
  • Dec 04 19:06
    lmakarov assigned #1442
  • Dec 04 19:06
    lmakarov opened #1442
  • Dec 04 19:04
    lmakarov synchronize #1439
  • Dec 04 17:50
    danshumaker commented #201
  • Dec 04 17:49
    danshumaker commented #201
  • Dec 03 17:09
    lmakarov commented #1152
  • Dec 03 05:45
    HiveForensicsAI commented #414
  • Dec 02 21:05
    DigitalFrontiersMedia commented #1420
  • Dec 02 21:00
    DigitalFrontiersMedia commented #1420
  • Dec 02 16:55
    sean-e-dietrich labeled #1420
  • Dec 02 16:55
    sean-e-dietrich labeled #1420
  • Dec 02 16:54
    sean-e-dietrich commented #1420
  • Dec 01 00:47
    lmakarov synchronize #1441
  • Nov 30 23:26
    lmakarov synchronize #1441
Andy Dempster
@BrizzleRocker
I have upgraded and no issues so far.
Ken Robinson
@kenrbnsn

None of my projects are working -- I can't see the web sites served by docksal.
Running Windows 10 Version 1909
Docker Desktop 2.4.0.0 (48506)
Fin 1.99.0
WSL Ubuntu 18.04

I started a new & empty project with
$ fin init

I got all the correct messages, which ended with:
Project URL: http://newtest.docksal

When I go to that URL, I get the error on my browser (Chrome)

newtest.docksal’s server IP address could not be found.

Leonid Makarov
@lmakarov

@kenrbnsn there have been multiple regressions with the recent Docker Desktop versions, which we had to address in a non-backward-compatible way, unfortunately.
Here are the options you have:

  1. Downgrade to Docker Desktop v2.1.0.5 and stick with it for the time being
  2. Switch to the new external docksal.site base domain
  3. Use fin hosts to manually manage DNS records

See : https://github.com/docksal/docksal/releases/tag/1.13.3

The first option would probably be your best bet for now.
Docker Desktop v2.3.0.2+ compatibility (without workaround) is pending a PR merge and a release
docksal/docksal#1419
Bharath Kondeti
@bharath-kondeti

Hey,

$ fin composer install gives composer not found in var/www

fin composer install
Composer could not find a composer.json file in /var/www
To initialize a project, please create a composer.json file as described in the https://getcomposer.org/ "Getting Started" section
This is on WSL
Can someone help me out
Corey Lewis
@cursiv3
I'm assuming you have that file in that dir? You installed compser etc on wsl not just windows ya?
Bharath Kondeti
@bharath-kondeti
Yes, the file is present and also i have installed composer on wsl
Leonid Makarov
@lmakarov
@bharath-kondeti in the project directory, run fin exec ls -la /var/www. What's the output?
If it's empty, then the host's filesystem did not mount correctly in Docker. fin exec mount | grep /var/www?
Jeff Brewster
@jlbrewster
I am having trouble getting even sample projects to start. I have tried all of the troubleshooting steps, but when I run 'fin init'/'fin start' I get no errors, but the browser says "server not found".
  • I am on Ubuntu 20.04 (apache2 disabled)
  • I have tried 'drupal8_boilerplate', and 'drupal8_boilerplate_composer' sample images
  • I have updated Docksal and confirmed my Docker installation
  • I have tried all of the troubleshooting steps on docksal.io (3x)
    When I run 'fin logs web' I get:
    web_1 | Configuring Apache2 environment variables... web_1 | [Tue Oct 27 18:09:06.265864 2020] [ssl:warn] [pid 1:tid 140484324903816] AH01909: web:443:0 server certificate does NOT include an ID which matches the server name web_1 | [Tue Oct 27 18:09:06.270192 2020] [ssl:warn] [pid 1:tid 140484324903816] AH01909: web:443:0 server certificate does NOT include an ID which matches the server name web_1 | [Tue Oct 27 18:09:06.271341 2020] [mpm_event:notice] [pid 1:tid 140484324903816] AH00489: Apache/2.4.35 (Unix) LibreSSL/2.6.5 configured -- resuming normal operations web_1 | [Tue Oct 27 18:09:06.271358 2020] [core:notice] [pid 1:tid 140484324903816] AH00094: Command line: 'httpd -D FOREGROUND'
    The other logs look OK to me as well...but maybe I am not seeing it?
Could those ^ ssl warnings be my problem?
Jeff Brewster
@jlbrewster
Output of fin ps:
d8_cli_1 /opt/startup.sh supervisord Up (healthy) 22/tcp, 3000/tcp, 9000/tcp d8_db_1 docker-entrypoint.sh mysqld Up (healthy) 0.0.0.0:32771->3306/tcp d8_web_1 httpd-foreground Up (healthy) 443/tcp, 80/tcp
Jeff Brewster
@jlbrewster
I'd like to add that I have some experience working with Docksal, but sometimes my environment falls off a cliff, and, as is the present situation, I don't know how to get it back. I guess I will go back to docker4drupal, and try to overcome all of the difficulties there..(maybe local LAMP?)
This may be the last time that I get immovably "stuck" with Docksal..(quite frustrated!)
Jeff Brewster
@jlbrewster
No matter what I do, going to http://192.168.64.100/ says "project missing".
Jeff Brewster
@jlbrewster
However, this morning, I had an instinct that the fin project was the problem, 'maybe I have not run the proper commands?' And remembered what the dev who introduced Docksal to me told me to do: 'fin init site'. (I don't think this is mentioned in docs; I was running 'fin init'). It appears that perhaps 'fin init site' runs different commands?)
I thought that worked (yes!) because I saw my Drupal site. 10 minutes later, the browser is saying "server not found". What the heck??
Jeff Brewster
@jlbrewster
OK. I have something to report back that hopefully will help others. It seems that the intermittent behavior I was seeing was due to the BROWSER! Firefox just does not work for my Docksal sites (dunno why). I suspect that every time I happened to use Chrome, it was fine, which frustrated my troubleshooting efforts. (May have even been the reason in times past when the project "went off a cliff" (because I happened to be using Firefox)? <<<<<------That's my story; I'll update the board if I find differently
Also, @bharath-kondeti : I have run into this from time to time. Have you run composer init to generate a composer.json file? Then you would need to run composer update or composer install to generate the vendor/bin folder. (I think the doc's are unclear on this point).
Leonid Makarov
@lmakarov

@jlbrewster the way we deal with *.docksal domain resolution is tricky and varies from platform to platform. Apparently (per your experience above), browsers can also add more moving parts and frustration to the mix.

Try switching to the new *.docksal.site public domain for your Docksal setup. This will yield identical results regardless of the OS and browser (as long as your machine has an internet connection and can reach public DNS servers)
https://docs.docksal.io/stack/configuration-variables/#docksal-dns-disabled

apetrovici
@apetrovici
Hi! I'm new around. I try to install magento 2.4 enterprise, which asks for elasticsearch 7. I've added in my .docksal/docksal.yml the elasticsearch service, as stated in documentation, but it installs elasticsearch 6.5.3 and the install dies at sample data. If I also add image: docker.elastic.co/elasticsearch/elasticsearch:7.9.3, dies with " Could not validate a connection to Elasticsearch. No alive nodes found in your cluster". Any help would be appreciated. Thanks.
fin config show
elasticsearch:
dns:
- 192.168.64.100
- 8.8.8.8
environment:
  ES_JAVA_OPTS: -Xms512m -Xmx512m
  bootstrap.memory_lock: "true"
hostname: elasticsearch
image: docker.elastic.co/elasticsearch/elasticsearch:7.9.3
logging:
  options:
    max-file: '10'
    max-size: 1m
ports:
- 9200/tcp
ulimits:
  memlock:
    hard: -1
    soft: -1
aclemensinquest
@aclemensinquest
Can someone assist me with "This site can’t be reached" issue? I reinstalled wsl and docker, still getting the error when accessing my site. I think this started to happen after docker update.
aclemensinquest
@aclemensinquest
Just noticed that install instructions for docksal mention very specific versions of ubuntu wsl and docker. Will try these now.
aclemensinquest
@aclemensinquest
So, even with correct versions of Ubuntu and Docker. I get an error message when trying to install docksal:
image.png
aclemensinquest
@aclemensinquest
Please disregard. I traversed github issues and found that enabling metadata for wsl will alleviate the issue: https://devblogs.microsoft.com/commandline/automatically-configuring-wsl/
image.png
in /etc/wsl.conf+ wsl hard reboot
Stefan Ivic
@stefanivic
Hello everyone, I am some profiling and I want to get as close to as possible to near native performance. Based on the looks of it, seems that not using any volumes and deveoping inside the container is my best bet. But I’ve been met with issues regarding file ownership and performance still not being near native. Is there an existing official or community owned stack for WordPress that’s using no volumes as default ?
Jeff Brewster
@jlbrewster
@stefanivic I'm not sure about WordPress, but for my Drupal Dockers, I was able to achieve massive performance gains by caching my volumes. This takes some massaging, depending on your needs, but I think it's what you are looking for (example: Caching Drupal core and things that don't change often). Something like this:
https://brandnewbox.com/notes/2019/09/docker-volume-cached/
Boris Doesborg
@batigolix
Has someone been able to use Composer 2 with docksal? Is there any documentation on this?
Shelane French
@shelane
Yes, I have. Our next CLI release will contain both composer 1 and 2 with 2 set as the default. If you want to do it now, it will be on a per project bases.
fin bash
sudo composer self-update2
That is a double hyphen with the 2.
Boris Doesborg
@batigolix
Great, Many Thanks @shelane
Jeff Brewster
@jlbrewster

I'm having Drupal install issues(related to db):
I fixed an issue with drush and now I can see some of the fields auto-populate. I figured out that, indeed, the 'fin config' settings are at least partially populating in the Drupal install window. However, I must still be missing something, because it still won't connect.

  • I have created user "user@db" in my database (cli)
  • I created database called "default" (cli)
    Here is my fin config output:
    `PROJECT_ROOT: /var/www/myproject
    DOCROOT: web
    VIRTUAL_HOST: myproject.docksal
    VIRTUAL_HOST_ALIASES: *.myproject.docksal
    IP: 192.168.64.100
    MYSQL: 192.168.64.100:32768

Docker Compose configuration

services:
cli:
dns:

- 192.168.64.100
- 8.8.8.8
environment:
  BLACKFIRE_CLIENT_ID: null
  BLACKFIRE_CLIENT_TOKEN: null
  COMPOSER_ALLOW_XDEBUG: '0'
  COMPOSER_DISABLE_XDEBUG_WARN: '0'
  DOCROOT: web
  DRUSH_ALLOW_XDEBUG: '0'
  DRUSH_OPTIONS_URI: myproject.docksal
  GIT_USER_EMAIL: ''
  GIT_USER_NAME: ''
  HOST_GID: '1000'
  HOST_UID: '1000'
  MYSQL_DATABASE: default
  MYSQL_HOST: db
  MYSQL_PASSWORD: user
  MYSQL_ROOT_PASSWORD: root
  MYSQL_USER: user
  PHP_IDE_CONFIG: null
  SECRET_ACAPI_EMAIL: null
  SECRET_ACAPI_KEY: null
  SECRET_ACQUIACLI_KEY: null
  SECRET_ACQUIACLI_SECRET: null
  SECRET_PLATFORMSH_CLI_TOKEN: null
  SECRET_SSH_PRIVATE_KEY: null
  SECRET_TERMINUS_TOKEN: null
  SSH_AUTH_SOCK: /.ssh-agent/proxy-socket
  VIRTUAL_HOST: myproject.docksal
  XDEBUG_CONFIG: remote_connect_back=0 remote_host=192.168.64.1
  XDEBUG_ENABLED: '0'
hostname: cli
image: docksal/cli:2.11-php7.3
labels:
  io.docksal.shell: bash
  io.docksal.user: docker
logging:
  options:
    max-file: '10'
    max-size: 1m
volumes:
- docksal_ssh_agent:/.ssh-agent:ro
- cli_home:/home/docker:rw
- /home/jeff/.docksal/tmp/myproject:/home/jeff/.docksal/tmp/myproject:ro
- project_root:/var/www:rw,nocopy,cached

db:
dns:

- 192.168.64.100
- 8.8.8.8
environment:
  MYSQL_ALLOW_EMPTY_PASSWORD: null
  MYSQL_DATABASE: default
  MYSQL_INITDB_SKIP_TZINFO: null
  MYSQL_ONETIME_PASSWORD: null
  MYSQL_PASSWORD: user
  MYSQL_RANDOM_ROOT_PASSWORD: null
  MYSQL_ROOT_PASSWORD: root
  MYSQL_USER: user
hostname: db
image: docksal/mysql:5.6-1.5
logging:
  options:
    max-file: '10'
    max-size: 1m
ports:
- 3306/tcp
volumes:
- db_data:/var/lib/mysql:rw
- project_root:/var/www:ro,nocopy,cached

web:
depends_on:
cli:
condition: service_started
dns:

- 192.168.64.100
- 8.8.8.8
environment:
  APACHE_BASIC_AUTH_PASS: null
  APACHE_BASIC_AUTH_USER: null
  APACHE_DOCUMENTROOT: /var/www/web
  APACHE_FCGI_HOST_PORT: cli:9000
hostname: web
image: docksal/apache:2.4-2.3
labels:
  io.docksal.cert-name: none
  io.docksal.permanent: "false"
  io.docksal.project-root: /var/www/myproject
  io.docksal.virtual-host: myproject.docksal,*.myproject.docksal,myproject.docksal.*
logging:
  options:
    max-file: '10'
    max-size: 1m
volumes:
- project_root:/var/www:ro,nocopy,cached

version: '2.1'`

Jeff Brewster
@jlbrewster

Can someone please help me confirm what the credentials are supposed to be ^? (I am not sure if I have a credential issue anymore).

I have (D8 install screen):

  • Database: 'default' *
  • Database username: 'user@db' *
  • Database password: 'user'
    Advanced Options:
    • Host: 'db' <-unsure?
    • Port: 3306
      *(values auto-populate)
      I have also tried host: 'web' as well as 'myproject.docksal', and various IP's
      My setup is new, "standard" Ubuntu 20.04.

If the above look correct, what should I look at next?

Jeff Brewster
@jlbrewster
I found a clue. My error ow reads:
SQLSTATE[HY000] [1045] Access denied for user 'user@db'@'172.19.0.3' (using password: NO).
I am confused about why this IP address(which is in my local ifconig)? Any ideas how to fix?
Leonid Makarov
@lmakarov

@jlbrewster see here https://docs.docksal.io/tools/drupal/

If you want to enter values manually during Drupal install, then use these values (pulled from your fin config output):

  MYSQL_DATABASE: default
  MYSQL_HOST: db
  MYSQL_PASSWORD: user
  MYSQL_USER: user
If you want to connect to the database from your host machine, then see docs here:
https://docs.docksal.io/service/db/access/
Jeff Brewster
@jlbrewster
Thanks, @lmakarov : )
That was actually a very important piece for my understanding of Docksal/Drupal. Since I started with Docker, I was unsure, even after using Docksal for a year, where "things" were. (They're right there in the 'fin config'! I appreciate your continued support, and the fact that you somehow have time to regularly help annoying users like me.
Leonid Makarov
@lmakarov
@jlbrewster np, you are welcome :)
Leonid Makarov
@lmakarov

@/all We are happy to announce that there will be no pull rate limits for Docksal images on Docker Hub 🐳. This applies to both authenticated as well as anonymous pulls.

https://twitter.com/docksalio/status/1331370086033100800

Michiel
@MichielHuijse

Hello, I have a question regarding solr. I am using the following documentation but cannot get a single core to connect:
https://docs.docksal.io/service/other/apache-solr/

my local.settings.php looks like:

$config['search_api.server.default_solr_server'] = [
  'name' => 'Solr Server (Overridden)',
  'backend_config' => [
    'connector' => 'standard',
    'connector_config' => [
       'protocol' => 'http',
       'host' => 'mylocalhostname.docksal',
       'port' => 8983,
       'path' => '/solr',
      'core' => 'user-owned',
    ],
  ],
];

My docksal.yml looks like:

services:
  solr:
    extends:
      file: ${HOME}/.docksal/stacks/services.yml
      service: solr
    hostname: solr
    image: docksal/solr:8.1
    volumes:
      - ${PROJECT_ROOT}/.docksal/etc/solr/conf:/var/lib/solr/conf:ro

And the folder structure for the conf is as follows:
.docksal/etc/solr/conf
In the conf I have put the searchapi solr conf file.
Do I need a core.properties file? It is nog clear from the documentation if you also need this with a single core.

Ricardo Amaro
@ricardoamaro
Hello everyone! Anyone seen @achekulaev lately? @lmakarov maybe?
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...
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