Docker on Logan's Nest

Home Assistant with DSM7

Thu, 04 Jan 2024 00:00:00 +0000

https://gist.github.com/maeneak/851e883eca7cddd7114f7eaed201ca9d has a pretty good guide in there.

Create a data directory & docker-compose file:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18


version: '3'

services:
 hassio:
 image: homeassistant/amd64-hassio-supervisor
 container_name: hassio_supervisor
 privileged: true
 security_opt:
 - seccomp:unconfined
 - apparmor:unconfined
 environment:
 - HOMEASSISTANT_REPOSITORY=homeassistant/qemux86-64-homeassistant
 - SUPERVISOR_SHARE=/volume1/docker/homeassistant
 - SUPERVISOR_NAME=hassio_supervisor
 volumes:
 - /volume1/docker/homeassistant:/data
 - /var/run/docker.sock:/var/run/docker.sock
 - /var/run/dbus:/var/run/dbus

Then run docker-compose up -d and you should be good to go.

fargate container healthcheck

Mon, 18 Jan 2021 00:00:00 +0000

Long story in short, unlike what https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_HealthCheck.html suggests, fargate doesn’t have curl.

For some reason it does have wget, so "command": [ "CMD-SHELL", "wget -q -O - ${healthcheck_endpoint} || exit 1" ] works as expected.

Selenoid Parallel CI testing

Tue, 12 May 2020 00:00:00 +0000

Selenoid is handy tool to manage test runner with minimum efforts.
As it uses own dependent containers by itself, need to maintain single Selenoid run per build agent.

docker-compose.yml

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37


services: 
 e2e-test-runner:
 networks:
 selenoid: null
 depends_on:
 - selenoid
 build:
 context: .
 dockerfile: end-to-end/Dockerfile
 environment:
 - BUILDKITE
 - NEXUS_USERNAME
 - NEXUS_PASSWORD
 - PAYLATER_VERSION
 - CHROME_PROFILE_DIR=/tmp/chrome_profile
 - SEL_JUP_SELENIUM_SERVER_URL=http://selenoid:4444/wd/hub/
 - GRADLE_USER_HOME=/app/.gradle
 volumes:
 - $PWD/end-to-end/build/reports:/app/end-to-end/build/reports
 - $PWD/build/reports:/app/build/reports
 - /var/run/docker.sock:/var/run/docker.sock


 selenoid:
 image: aerokube/selenoid:latest-release
 networks:
 selenoid: null
 volumes:
 - "/tmp/selenoid/video:/opt/selenoid/video:delegated"
 - "/tmp/selenoid/logs:/opt/selenoid/logs:delegated"
 - "$PWD/end-to-end/selenoid:/etc/selenoid:delegated"
 - "/var/run/docker.sock:/var/run/docker.sock"
 expose:
 - "4444"
 environment:
 - OVERRIDE_VIDEO_OUTPUT_DIR=/tmp/selenoid/video
 command: ["-conf", "/etc/selenoid/browsers.json", "-video-output-dir", "/opt/selenoid/video", "-log-output-dir", "/opt/selenoid/logs","-save-all-logs","-disable-privileged", "-container-network", "selenoid"]

CI Pipeline (BK)

Salesforce CLI with Docker in AWS

Fri, 28 Jun 2019 00:00:00 +0000

Auth was the tricky part as the normal auth requires a browser session rather than taking it from the CLI prompt.

Step 1. Create Dockerfile

1
2
3
4


FROM node:9.9.0-alpine 
RUN npm install sfdx-cli --global 
RUN sfdx --version 
RUN sfdx plugins --core

Step 2. Generate auth URL from your laptop and push into SSM

Selenium test with docker-compose

Tue, 23 May 2017 00:00:00 +0000

Sample config file when using selenium standalone during test.

docker-compose YAML

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20


version: '3'
services:
 test:
 depends_on:
 - selenium
 environment:
 - E2ETEST_HOST=test
 - SELENIUM_PORT=4444
 - SELENIUM_HOST=selenium
 build:
 context: .
 dockerfile: Dockerfile
 ports:
 - "80:80"
 - "443:443"
 command: run_test.sh
 selenium:
 image: selenium/standalone-chrome
 ports:
 - "4444:4444"

nightwatch config sample