Samuel's questions

I want to write a PowerShell script that will create a number of running docker containers on boot of the machine. The problem I'm running into is that despite the com.docker.service service running, the backend for Docker Desktop (I presume WSL2) is still getting ready.

I can manually recreate this behaviour by running docker version or similar when the system is starting. It will show:

error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/json": open //./pipe/docker_engine: The system cannot find the file specified.

However after a couple of minutes (once the backend has come up) then the command will start working:

Client:
 Cloud integration: v1.0.22
 Version:           20.10.11
 API version:       1.41
 Go version:        go1.16.10
 Git commit:        dea9396
 Built:             Thu Nov 18 00:42:51 2021
 OS/Arch:           windows/amd64
 Context:           default
 Experimental:      true

How can I reliably wait for Docker Desktop to be ready before trying to start containers? I suspect the solution might be waiting for the pipe file or similar rather than a service.

I'm having a small amount of trouble pinning down exactly how I want to architect my Docker Swarm cluster. Currently it consists of:

• 1 MariaDB which will need to have persistent storage suitable for a database.

• 2 x MediaWiki servers which will need to have persistent storage suitable for storing images, videos and other media files.

• Some kind of ingress that will map a domain name to each of the MediaWiki servers based on domain name.

I could do with some feedback on possible ways of architecting this. Ideally I'd like all three servers to contain instances of the MediaWiki application or perhaps 2 servers and 1 dedicated host server for the database. One MediaWiki application receives around 20x the traffic of the other so would benefit running over multiple machines.

The trouble I'm having is trying to persist data between deployments. I'm currently considering something like CephFS with block storage mounted into one master host and two slave instances replicating from that.

I also have not explored the ingress component yet but I'm assuming I can configure some kind of Nginx server, ideally with Lets Encrypt enabled, that will proxy traffic to either of the MediaWiki hostnames depending on the incoming domain name, however this may be a naive assumption.

I'm trying to configure two applications to be served up by nginx. The first seems to be working fine and I duplicated the config for the second, however I'm having some problems.

I'm running a Sinatra server backed with Unicorn using sockets to pass the upstream information. I can reach the root domain fine (api.richardson.co.nz) and everything seems to be working ok, however as soon as I try to access a path off the root domain (api.richardson.co.nz/games) I get a "not found" error.

Here is my nginx conf file:

worker_processes 1;
user nginx web;
pid /tmp/nginx.pid;
error_log /var/www/knowyourgenre.com/shared/log/nginx.error.log;

events {
  worker_connections 1024; # increase if you have lots of clients
  accept_mutex off; # "on" if nginx worker_processes > 1
  use epoll; # enable for Linux 2.6+
}

http {
  include mime.types;
  default_type application/octet-stream;
  access_log /tmp/nginx.access.log combined;
  sendfile on;
  tcp_nopush on; # off may be better for *some* Comet/long-poll stuff
  tcp_nodelay off; # on may be better for some Comet/long-poll stuff
  gzip on;
  gzip_http_version 1.0;
  gzip_proxied any;
  gzip_min_length 500;
  gzip_disable "MSIE [1-6]\.";
  gzip_types text/plain text/html text/xml text/css
             text/comma-separated-values
             text/javascript application/x-javascript
             application/atom+xml;

  upstream app_server {
    server unix:/var/www/knowyourgenre.com/current/unicorn.sock fail_timeout=0;
    server localhost:8080 fail_timeout=0;
  }

  upstream api {
    server unix:/var/www/api/unicorn.sock fail_timeout=0;
    server localhost:8081 fail_timeout=0;
  }

  server {
    listen 80; # for Linux
    client_max_body_size 4G;
    server_name .knowyourgenre.com;
    keepalive_timeout 5;
    root /var/www/knowyourgenre.com/current/public/;
    try_files $uri/index.html $uri.html $uri @app;

    location @app {
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header Host $http_host;
      proxy_redirect off;
      proxy_pass http://app_server;
    }

    error_page 500 502 503 504 /500.html;
    location = /500.html {
      root /path/to/app/current/public;
    }
  }

  server {
    listen 80; # for Linux
    client_max_body_size 4G;
    server_name .richardson.co.nz;
    keepalive_timeout 5;
    root /var/www/api;
    try_files $uri/index.html $uri.html $uri @app;

    location @app {
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header Host $http_host;
      proxy_redirect off;
      proxy_pass http://api;
    }

    # Rails error pages
    error_page 500 502 503 504 /500.html;
    location = /500.html {
      root /path/to/app/current/public;
    }
  }

}

Would an error in the upstream server cause a "not found" to be returned? I'm pretty sure everything is working within the Sinatra server but I may have missed something.

Pretty much what the title of the question is. On my local machine I've been setting up named virtual hosts for each clients website that I'm working on. It would be quicker if I could specify a wildcard rule that:

http://[hostname]

refers to files in

~/Sites/[hostname]/

Automatically without having to create an entry for each (which I currently have now)

Is this possible?