I had an issue on the weekend where the backup command, running in a docker container:

restic backup /shared

Would always report that all files were new, but when run repeatedly in the same container would work a treat.

With Docker Desktop for Mac, its finally possible to forward the ssh agents from the host through to a container. Wooohooo.

But. If you are accessing the Mac itself via ssh, then any ssh identities that are forwarded cannot be forwarded into the container.

Eg, I was on Linux, ssh'ing to the mac and trying to bring up the docker containers with the identity. It doesn't work, couldn't get the identities to come through.

Have just upgraded to 20.04 and this time have disabled snaps completely.

https://www.kevin-custer.com/blog/disabling-snaps-in-ubuntu-20-04/

Thanks Kevin and commenters.

I had an issue with running site-install on a Drupal 9 site where the exported views in the config/optional directory were not being imported.

After some diagnosis, the reason is that there was a change and now the optional config is imported before the install profile is activated - See change record - https://www.drupal.org/node/3118908

My problem was there were user roles in the config/install of the profile that the exported views depended on.

With the release of Drupal 9 just days away, I wanted to take it for a spin, and updated the Shepherd scaffold we use for OpenShift deployments so that things work nicely. If you already have docker, docker-compose & composer installed, try these steps to give it a spin.

Create a new project using the recommended method of the release candidate:

With Ubuntu 19.10, they moved Chromium from a .deb to a snap install only.

This makes browser startup times much slower and causes weird effects when saving files, and basically made me stop using Chromium as a consequence :-(

Today I found this article which gave the info on how to switch back to a .deb installed chromium and get back to normal.

https://shevchuk.co/notes/2019/12/13/install-chromium-on-ubuntu-1910-from-debian-instead-of-snap

Are you still stuck using a VM and NFS to edit your website code?
Did you know you can run a fairly simple process inside a running VM that will convert it to an LXD container?

It took a bit of figuring out, but the reduced memory usage, increased speed and easier directory sharing make it will worth the effort.

This assumes an existing VM which you can already log into. The approximate steps required are:
1. Install lxd - I initially installed with apt, but its an older version, so probably better to install the snap instead.

Let me take you on an adventure.

Today I needed to access a service inside a corporate network, but the service is firewalled from external use, and also from access via the VPN.

The suggestion was to use a machine already internal to the network and some port forwarding to get around this restriction. Ahah, I can get around this with a small container on the OpenShift cluster I thought.

So I need a tiny container just for forwarding ports. Google turned up - https://github.com/derkork/socat-openshift.

Warning - this reduces security

Find the id of the container, you can list active containers with:

pct list

Edit the container config like:

vim /etc/pve/lxc/113.conf

Add the extra lines:

lxc.apparmor.profile: unconfined
lxc.cgroup.devices.allow: a
lxc.cap.drop:

Shutdown and restart the container.

To enable aufs/overlay in the container, it actually needs to be loaded on the proxmox host, this can be done with:

Sometimes you need to push images into the OpenShift registry locally for testing, the steps involved are below. Note that I start/stop local Openshift development with a command which includes:

BASE_DIR="/openshift/project"
export OPENSHIFT=$(ip addr show docker0 | grep "inet\b" | awk '{print $2}' | cut -d/ -f1)
oc cluster up --base-dir=${BASE_DIR} --public-hostname=${OPENSHIFT}

Which means it consistently listens on 172.17.0.1 which is available from within and outside of the OpenShift cluster, which 127.0.0.1 isn't.