Trying to use the Docker API to create/stop/delete a container gives the error
client version 1.43 is too new. Maximum supported API version is 1.41
Use the following
export DOCKER_API_VERSION=1.41
as described here
To sort the files in a directory use the following
du -sh -- * | sort -hTaken from https://unix.stackexchange.com/a/4682
When using the k8up annotations for a postgresql backup with :
k8up.io/backupcommand: /bin/bash -c 'pg_dumpall --clean | gzip --stdout
do not finish correctly, and as a result the gunzip complains about "unexpected end of file"
There is a workaround by first saving the file and then sending it to the standard output with
k8up.io/backupcommand: /bin/bash -c 'pg_dumpall --clean | gzip -c > /tmp/backup.gz
&& cat /tmp/backup.gz && rm /tmp/backup.gz'Thanks Simon Beck for the suggestion https://community.appuio.ch/channel/k8up/thread/j8AcG6ZjgGbQAzth5?msg=xgTanRqqJbBkNj9sd
After upgrading a PostgreSQL instance from version 9.6 to the currently latest version 15.3, your application cannot connect to the server, giving an authentication error even if the user/password used is still the same.
This seems to be the result of a change in the method used in the pg_hba.conf file.
Version 9.6 uses md5 but version 15.3 uses scram-sha-256
Changing this in the file pg_hba.conf file from scram-sha-256 to md5 and reloading the configuration file from inside the database with select pg_reload_conf(); , results in the application being able to connect to the database server again.
Update: It is possible to use the recommended scram-sha-256 hash, by doing the following:
#password_encryption = scram-sha-256 # scram-sha-256 or md5 in file /var/lib/postgresql/data/pgdata/postgresql.confselect pg_reload_conf();production=# alter user user_name with password 'password';You want to download a copy of your gitlab backup (ie when upgrading to version 7.0.0 as described in [here](https://docs.gitlab.com/charts/installation/database_upgrade.html#steps-for-upgrading-the-bundled-postgresql) ).
Login to the toolbox pod and get the credentials file for s3
cat /etc/gitlab/.s3cfg
Create a new file locally (ie ~/.s3cfg_gitlab) and then download the file locally with
s3cmd get s3://gitlab-backups/database_upgrade_6_gitlab_backup.tar 20230531_gitlab_backup.tar -c ~/.s3cfg_gitlabWhen using yaml to json conversion as it happens when using Terraform’s helm provider with a helm chart’s values.yaml file, it won’t be possible to check and get any useful validation errors, even when your terraform plan is run.
In order to check before running your plan or if you have any errors you can use yq passing as below using the values.yaml file
yq -p yaml -o json values.yamlTo display the results of a postgresql query as a table (in the example postgresql runs as a docker container locally) use something like the following
psql -h localhost -p 5555 -U postgres database_name -xc 'select * from table_name where id=29'When trying to use Nextcloud’s occ (ownCloud Console) command and it’s not possible to use sudo or su (installation on Debian GNU/Linux 11), you can try with the following command (you may have to change the paths to php and occ).
runuser --user www-data -- /usr/local/bin/php /var/www/html/occ user:list
The Helm installation order can be seen here
Trying to use a gcloud asdf installation it fails with the error:
gcloud version
ERROR: gcloud failed to load: No module named '_sqlite3'
After installing various components (readline, tk etc) the last one to install to make gcloud work is liblzma-dev (sudo apt install liblzma-dev)
Then gcloud works
gcloud version
Google Cloud SDK 420.0.0
bq 2.0.86
bundled-python3-unix 3.9.16
core 2023.02.24
gcloud-crc32c 1.0.0
gsutil 5.20
Updates are available for some Google Cloud CLI components. To install them,
please run:
$ gcloud components update