teracyhq / docker-files

Teracy docker-files project to build common Docker images

Teracy docker-files

Teracy project to create Docker images.

How to use

Follow README.md files located at each Docker image directories.

• Push to multiple docker registries:

  • By default, built docker images will be pushed to the github container registry: ghcr.io/${GITHUB_REPOSITORY}
  • To add more docker registries, you need to add REGISTRIES secret environment variable on github actions, for example: ghcr.io/teracyhq/docker-files, docker.io/teracy
  • Make sure to configure authorization for the configured registries, see more: https://github.com/teracyhq-incubator/.github#docker-multiple-login and https://github.com/teracyhq-incubator/.github#docker-build-push-sign

• Docker image name prefix:

  • Sometimes you need to add prefix to the docker image
  • For example, by default, ghcr.io/teracyhq/docker-files/ubuntu, you can change to ghcr.io/teracyhq/docker-files/teracy-ubuntu by setting IMG_NAME_PREFIX secret environment variable on github actions to teracy-

• Enable/disable docker push:

  • By default, docker images will be pushed when new commits are pushed to the master branch
  • To disable the docker push, set PUSH_ENABLED secret environment variable to false

How to contribute

• Fork this repo (it's recommened to renamed your forked repo to teracy-docker-files)

• Start creating new Docker images to be shared within our community

LICENSE

MIT license. More details on the LICENSE file.

docker-files's Issues

Should upgrade teracy/google-cloud-sdk image

• upgrade the Ubuntu image to 18.04.
• upgrade the gcloud sdk installation.
• upgrade the kubectl.

should upgrade ubuntu image to 18.04

upgrade teracy/ubuntu image to 18.04

should add angular-cli 1.0.0-beta.31 tag

and remove 1.0.0-beta.26, 1.0.0-beta.28 from the build, we will not continue maintaining old releases of angular-cli.

Chrome_no_sandbox not registered in pipeline

In my GitLab pipeline, I have setup the test job as follows:

test:
  image: teracy/angular-cli:latest
  stage: testing
  script:    
    - npm install
    - ng test --browsers Chrome_no_sandbox --watch=false --code-coverage
  cache:
    key:
      files:
        - package-lock.jsonnode
    paths:
      - node_modules
    policy: pull
  only:
    - tags

Now when I run this pipeline, The ng test command fails with the output:

$ ng test --browsers Chrome_no_sandbox --watch=false --code-coverage
Your global Angular CLI version (15.2.4) is greater than your local version (15.1.6). The local Angular CLI version is used.
To disable this warning use "ng config -g cli.warnings.versionMismatch false".
- Generating browser application bundles (phase: setup)...
✔ Browser application bundle generation complete.
26 03 2023 13:17:18.838:INFO [karma-server]: Karma v6.4.1 server started at http://localhost:9876/
26 03 2023 13:17:18.841:INFO [launcher]: Launching browsers Chrome_no_sandbox with concurrency unlimited
26 03 2023 13:17:18.842:ERROR [launcher]: Cannot load browser "Chrome_no_sandbox": it is not registered! Perhaps you are missing some plugin?
26 03 2023 13:17:18.842:ERROR [karma-server]: Error: Found 1 load error
    at Server.<anonymous> (/builds/oCf3nwxa/0/[MASKED]/web-app/node_modules/karma/lib/server.js:243:26)
    at Object.onceWrapper (events.js:519:28)
    at Server.emit (events.js:412:35)
    at emitListeningNT (net.js:1365:10)
    at processTicksAndRejections (internal/process/task_queues.js:[81](https://gitlab.argoplan.nl/clients/ru6gp1zjn9/argoplan/web-app/-/jobs/596#L81):21)
✔ Browser application bundle generation complete.
✔ Browser application bundle generation complete.
Cleaning up project directory and file based variables
00:00
ERROR: Job failed: command terminated with exit code 1

Why does it say that my "Chrome_no_sandbox" is not registered?

should improve the teracy/node-ruby image

• use the latest node.js version by default (instead of current 6.10)
• create more versions (tags):

• teracy/node-ruby:latest
• teracy/node-ruby:6.10
• teracy/node-ruby:6.11
• teracy/node-ruby:8.6

Running `ng test` fails to start chrome browser

Hi, thanks for the image. I'm having trouble getting ng test to run. Here is my docker-compose.yaml:

version: '2'
services:
  test-web-app:
    image: teracy/angular-cli
    command:
      - ng
      - test
    working_dir: /usr/src
    volumes:
      - "./:/usr/src"

when I run docker-compose run test-web-app

I get the output

Starting virtual X frame buffer: Xvfb.
Executing command ng test
25 01 2017 14:35:22.023:WARN [karma]: No captured browser, open http://localhost:9876/
25 01 2017 14:35:22.047:INFO [karma]: Karma v1.2.0 server started at http://localhost:9876/
25 01 2017 14:35:22.049:INFO [launcher]: Launching browser Chrome with unlimited concurrency
25 01 2017 14:35:22.093:INFO [launcher]: Starting browser Chrome
25 01 2017 14:35:22.406:ERROR [launcher]: Cannot start Chrome

25 01 2017 14:35:23.481:INFO [launcher]: Trying to start Chrome again (1/2).
25 01 2017 14:35:23.581:ERROR [launcher]: Cannot start Chrome

25 01 2017 14:35:23.803:INFO [launcher]: Trying to start Chrome again (2/2).
25 01 2017 14:35:23.927:ERROR [launcher]: Cannot start Chrome

25 01 2017 14:35:24.087:ERROR [launcher]: Chrome failed 2 times (cannot start). Giving up.

Trying to run command it is displayed /bin/bash No such file or directory

I tried to run this command on my terminal
docker run -it -v "$PWD":/usr/src -w /usr/src -p "3000:3000" teracy/create-react-app /bin/bash root@4b15ab7dbf21:/usr/src# create-react-app . root@4b15ab7dbf21:/usr/src# HOST=0.0.0.0 && npm start

I would like to confirm that should I change some parameter to make it run on my machine?

This is an error message that I got it

bin/bash: root@4b15ab7dbf21:/usr/src#: No such file or directory

should have teracy/duplicity Docker image

to use http://duplicity.nongnu.org/duplicity.1.html

"ng build" failing but working on local environment

Hi Team,

I am facing this issue from past 4 days. I am using the image teracy/angular-cli to build my project on gitlab. The issue is, with the latest code, the build is failing on gitlab where I use the the image of angular-cli from docker-files. But the same is running successfully on my local enviroment. You can find the logs attached.

Also, my local angular-cli version is 1.0.0-rc.1. You can find the packages.json file below.

{
  "name": "trust-angular2",
  "version": "0.0.0",
  "license": "MIT",
  "angular-cli": {},
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "lint": "tslint \"src/**/*.ts\" --project src/tsconfig.json --type-check && tslint \"e2e/**/*.ts\" --project e2e/tsconfig.json --type-check",
    "test": "ng test",
    "pree2e": "webdriver-manager update --standalone false --gecko false",
    "e2e": "protractor"
  },
  "private": true,
  "dependencies": {
    "@agm/core": "^1.0.0-beta.1",
    "@angular/common": "^2.3.1",
    "@angular/compiler": "^2.3.1",
    "@angular/core": "^2.3.1",
    "@angular/flex-layout": "^2.0.0-rc.1",
    "@angular/forms": "^2.3.1",
    "@angular/http": "^2.3.1",
    "@angular/material": "^2.0.0-beta.2",
    "@angular/platform-browser": "^2.3.1",
    "@angular/platform-browser-dynamic": "^2.3.1",
    "@angular/router": "^3.3.1",
    "@angular2-material/core": "^2.0.0-alpha.7-4",
    "@asymmetrik/ngx-leaflet": "^2.5.1",
    "@ng-idle/core": "^2.0.0-beta.9",
    "@ng-idle/keepalive": "^2.0.0-beta.9",
    "@types/leaflet": "^1.2.2",
    "core-js": "^2.4.1",
    "leaflet": "^1.2.0",
    "ng2-cache-service": "^1.0.2",
    "ng2-cookies": "^1.0.6",
    "ng2-flex-layout": "^0.1.5",
    "ng2-img-cropper": "^0.9.0",
  },
  "devDependencies": {
    "@angular/cli": "^1.0.0-rc.1",
    "@angular/compiler-cli": "^2.3.1",
    "@types/google.analytics": "0.0.33",
    "@types/googlemaps": "^3.29.0",
    "@types/jasmine": "2.5.38",
    "@types/node": "^6.0.42",
    "codelyzer": "~2.0.0-beta.1",
    "protractor": "~4.0.13",
    "ts-node": "1.2.1",
    "tslint": "^4.3.0",
    "typescript": "~2.0.3"
  }
}

Also, below is my npm version on local.

npm: '5.5.1',
 ares: '1.10.1-DEV',
 http_parser: '2.7.0',
 icu: '56.1',
 modules: '48',
 node: '6.11.1',
 openssl: '1.0.2k',
 uv: '1.11.0',
 v8: '5.1.281.103',
 zlib: '1.2.11' 

In short the error I am receiving while deploying with teracy/angular-cli on gitlab is

ERROR in Error encountered resolving symbol values statically. Could not resolve @asymmetrik/ngx-leaflet/dist relative to /builds/vernuso/trust/src/app/task/task.module.ts., resolving symbol TaskModule in /builds/vernuso/trust/src/app/task/task.module.ts, resolving symbol TaskModule in /builds/vernuso/trust/src/app/task/task.module.ts, resolving symbol TaskModule in /builds/vernuso/trust/src/app/task/task.module.ts

ERROR in /builds/vernuso/trust/src/app/task/task.module.ts (2,31): Cannot find module '@asymmetrik/ngx-leaflet/dist'.)

ERROR in ./src/app/task/task.module.ts
Module not found: Error: Can't resolve '@asymmetrik/ngx-leaflet/dist' in '/builds/vernuso/trust/src/app/task'
@ ./src/app/task/task.module.ts 11:0-61
@ ./src/app/app.module.ts
@ ./src/main.ts
@ multi ./src/main.ts
logs.txt

angular-cli: cannot find Chrome binary

Hey, I wanted to use your teracy/angular-cli image to run angular-cli e2e tests.

i did the following steps:

1. docker run --rm -it -v $(pwd):/opt -w /opt teracy/angular-cli /bin/bash
2. ng new test123
3. cd test123
4. ng e2e

ng e2e fails with the following error:

** NG Live Development Server is running on http://localhost:49152 **
Hash: 6648ff5c35778096f3ee
Time: 8065ms
chunk    {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 158 kB {4} [initial] [rendered]
chunk    {1} main.bundle.js, main.bundle.js.map (main) 3.62 kB {3} [initial] [rendered]
chunk    {2} styles.bundle.js, styles.bundle.js.map (styles) 9.77 kB {4} [initial] [rendered]
chunk    {3} vendor.bundle.js, vendor.bundle.js.map (vendor) 2.37 MB [initial] [rendered]
chunk    {4} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered]
webpack: Compiled successfully.
[07:41:40] I/file_manager - creating folder /opt/test123/node_modules/protractor/node_modules/webdriver-manager/selenium
[07:41:41] I/downloader - curl -o /opt/test123/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.28.zip https://chromedriver.storage.googleapis.com/2.28/chromedriver_linux64.zip
[07:41:41] I/update - chromedriver: unzipping chromedriver_2.28.zip
[07:41:41] I/update - chromedriver: setting permissions to 0755 for /opt/test123/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.28
[07:41:41] I/launcher - Running 1 instances of WebDriver
[07:41:41] I/direct - Using ChromeDriver directly...
[07:41:41] E/launcher - unknown error: cannot find Chrome binary
  (Driver info: chromedriver=2.28.455506 (18f6627e265f442aeec9b6661a49fe819aeeea1f),platform=Linux 3.16.0-4-amd64 x86_64)
[07:41:41] E/launcher - WebDriverError: unknown error: cannot find Chrome binary
  (Driver info: chromedriver=2.28.455506 (18f6627e265f442aeec9b6661a49fe819aeeea1f),platform=Linux 3.16.0-4-amd64 x86_64)
    at WebDriverError (/opt/test123/node_modules/selenium-webdriver/lib/error.js:27:5)
    at Object.checkLegacyResponse (/opt/test123/node_modules/selenium-webdriver/lib/error.js:505:15)
    at parseHttpResponse (/opt/test123/node_modules/selenium-webdriver/lib/http.js:509:13)
    at doSend.then.response (/opt/test123/node_modules/selenium-webdriver/lib/http.js:440:13)
    at process._tickCallback (internal/process/next_tick.js:109:7)
From: Task: WebDriver.createSession()
    at Function.createSession (/opt/test123/node_modules/selenium-webdriver/lib/webdriver.js:777:24)
    at Function.createSession (/opt/test123/node_modules/selenium-webdriver/chrome.js:709:29)
    at Direct.getNewDriver (/opt/test123/node_modules/protractor/lib/driverProviders/direct.ts:90:25)
    at Runner.createBrowser (/opt/test123/node_modules/protractor/lib/runner.ts:225:39)
    at q.then.then (/opt/test123/node_modules/protractor/lib/runner.ts:391:27)
    at _fulfilled (/opt/test123/node_modules/protractor/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/opt/test123/node_modules/protractor/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/opt/test123/node_modules/protractor/node_modules/q/q.js:796:13)
    at /opt/test123/node_modules/protractor/node_modules/q/q.js:556:49
    at runSingle (/opt/test123/node_modules/protractor/node_modules/q/q.js:137:13)
    at flush (/opt/test123/node_modules/protractor/node_modules/q/q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:73:7)
    at process._tickCallback (internal/process/next_tick.js:104:9)
[07:41:41] E/launcher - Process exited with error code 199

Any Idea what could be the issue? Thanks!

should add angular-cli:1.0.0-beta.30

npm install @angular/cli instead of angular-cli

Dind on Mac OS: Cannot connect to the Docker daemon at unix:///var/run/docker.sock

I run on Mac OS next command from README:
docker run --rm -it --link docker -v $(pwd):$(pwd) -w $(pwd) teracy/ubuntu:16.04-dind-17.06.0-ce bash
Then inside container I run "docker version" and see next error
"Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
".
Please assist

should support develop branch for development

follow our standard git flow, the develop branch should publish dev_<IMG_TAG> docker image tag.

Unit test failed in the latest angular-cli docker image

Hi,

The latest angular-cli docker image made my unit test failed, below are errors:

27 09 2017 18:32:53.394:ERROR [karma]: Error: /builds/ultralinq/htmlviewer/node_modules/@angular/core/src/di/reflective_provider.d.ts (87,123): Cannot find name ‘Map’.,/builds/ultralinq/htmlviewer/node_modules/@angular/core/src/di/reflective_provider.d.ts (87,165): Cannot find name ‘Map’.,/builds/ultralinq/htmlviewer/node_modules/rxjs/Observable.d.ts (69,60): Cannot find name ‘Promise’

I switched back to the old version 1.0.0_develop, it works well.

update README for the packer Docker image

How to use

should add aws-cli Docker image

to use aws-cli

should use standard /mnt/data instead of /data for aws-cli volume

see more: https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

should use less CI_ env vars

reduce CI_ env vars to these only:

# add more arguments from CI to the image so that `$ env` should reveal more info
ARG CI_BUILD_ID
ARG CI_BUILD_REF
ARG CI_REGISTRY_IMAGE
ARG CI_BUILD_TIME

should replace travis-ci by github actions

We got a lot of failed builds recently that need fixing https://travis-ci.org/github/teracyhq/docker-files/builds

should make sure xtrabackup has "ncat" installed

xtrabackup:buster-8.0 is required to have ncat for the mysqlha helm chart to work https://github.com/teracyhq/helm-charts/blob/main/charts/mysqlha/templates/statefulset.yaml#L59

should fix failed build job

we need to get all the jobs to be passed

https://travis-ci.org/teracyhq/docker-files/builds/515955654

Tag for Angular CLI 1.7

My team has been adding this line to our Dockerfiles to update Angular CLI to 1.7:

FROM teracy/angular-cli:1.5.0
RUN npm update -g @angular/[email protected]

Is it possible to release a tag for Angular CLI 1.7 so we don't have to do this? I looked into it, but it seems to be an environmental setting for the Travis build. If there's any way I can help, just let me know, happy to submit a PR.

Can't run tests from Ubuntu server

I have a brand new Ubuntu 18.04 server with Docker CE installed on it. I am trying to build my angular 7 cli project and have been getting an error and am unable to run my test.

Here is my Dockerfile

FROM teracy/angular-cli:7.3 as build

WORKDIR /app
COPY /Rubbl.Web.Website/package*.json ./
RUN npm i

COPY ./Rubbl.Web.Website .

# Run unit tests
RUN npm run test-headless

# Copy unit test results to /test
WORKDIR /app/src/test-results
RUN mkdir /test
RUN cp *.xml /test

WORKDIR /app
RUN mkdir /test/coverage
RUN cp -r coverage/* /test/coverage
RUN ng build --prod

WORKDIR /publish
RUN cp -r /app/dist/* ./

FROM nginx AS publish

RUN apt-get update
RUN apt-get install gettext -y

WORKDIR /test-results
COPY --from=build /test .

WORKDIR /app
COPY --from=build /publish/rubbl-web-website /usr/share/nginx/html
RUN rm /etc/nginx/conf.d/default.conf
COPY default.conf /etc/nginx/conf.d/
COPY ./startup.sh .

RUN chmod +x ./startup.sh

ENTRYPOINT ["/bin/bash", "-c", "./startup.sh"]

My Karma config:

// Karma configuration file, see link for more information
// https://karma-runner.github.io/1.0/config/configuration-file.html
process.env.CHROME_BIN = require('puppeteer').executablePath();

module.exports = function (config) {
  config.set({
    basePath: '',
    frameworks: ['jasmine', '@angular-devkit/build-angular'],
    plugins: [
      require('karma-jasmine'),
      require('karma-chrome-launcher'),
      require('karma-jasmine-html-reporter'),
      require('karma-coverage-istanbul-reporter'),
      require('@angular-devkit/build-angular/plugins/karma'),
      require('karma-junit-reporter')
    ],
    client: {
      clearContext: false // leave Jasmine Spec Runner output visible in browser
    },
    captureTimeout: 60000,
    browserDisconnectTimeout: 10000,
    browserDisconnectTolerance: 1,
    browserNoActivityTimeout: 60000,
    coverageIstanbulReporter: {
      dir: require('path').join(__dirname, '../coverage/rubbl-web-website'),
      reports: ['html', 'lcovonly', 'text-summary', 'cobertura'],
      fixWebpackSourcePaths: true
    },
    reporters: ['progress', 'kjhtml', 'junit'],
    port: 9876,
    colors: true,
    logLevel: config.LOG_INFO,
    autoWatch: true,
    browsers: ['Chrome', 'ChromeHeadless'],
    customLaunchers: {
      ChromeHeadlessCI: {
        base: 'ChromeHeadless',
        flags: ['--no-sandbox', '--disable-translate', '--disable-extensions']
      }
    },
    singleRun: false,
    files: [
      "./assets/environment/environment.js",
    ],
    junitReporter: {
      outputDir: 'test-results', // results will be saved as $outputDir/$browserName.xml
      outputFile: undefined, // if included, results will be saved as $outputDir/$browserName/$outputFile
      suite: '', // suite will become the package name attribute in xml testsuite element
      useBrowserName: true, // add browser name to report and classes names
      nameFormatter: undefined, // function (browser, result) to customize the name attribute in xml testcase element
      classNameFormatter: undefined, // function (browser, result) to customize the classname attribute in xml testcase element
      properties: {}, // key value pair of properties to add to the <properties> section of the report
      xmlVersion: null // use '1' if reporting to be per SonarQube 6.2 XML format
    }
  });
};

And here is the error I am getting:

should support different versions of angular-cli

for example:
teracy/angular-cli:1.0.0-beta.26
teracy/angular-cli:1.0.0-beta.28
teracy/angular-cli:1.0.0-beta.28.3
teracy/angular-cli:latest

should use yarn as default instead of npm for angular-cli, create-react-app

use yarn by default instead of npm.

should have jenkins-dod Docker image

so that we could use it to provision a Jenkins server with docker, docker-compose support.

related: http://container-solutions.com/running-docker-in-jenkins-in-docker/

should docker push only on master branch

• master => tag: latest
• develop => tag: dev
• others => tag: normalized branch name

export IMG_TAG=`echo $CI_BUILD_REF_NAME | sed -e 's/[\/]/-/g' | sed -e 's/[\#]//g';`

should add httpie-jwt-auth docker image

https://github.com/teracyhq/httpie-jwt-auth

so that everyone can use this right away

Should use latest version of Angular CLI

should create semver docker image

to install https://www.npmjs.com/package/semver and use it for semver related tasks

Updating Angular CLI to NPM 5/Node 8

Any reason not to do this? NPM 5 adds locking, which is a really nice feature, especially for Angular which seems to keep releasing breaking (or semi-breaking) changes in minor version updates.

I am happy to submit a PR as I get a lot of use out of your Dockerfile and am happy to give something back 😄

should create different versions of Ubuntu (LTS) along with different version of Docker

so that we can have a wide range of choices.

• Ubuntu 14.04, 16.04
• Docker from 11.x and up

use the 64-bit OS

tagging convention:

teracy/<platform>:<platform_version>-dind-<docker_version>

For example: teracy/ubuntu:16.04-dind-1.11.1

angular-cli docker-files

I noticed while working with the angular-cli example it says:

root@265dcf6e7241:/opt/new-ng2-app# ng set --global packageManager=yarn
and then:

$ cd new-ng-app

There is no new-ng-app at that point? It seems like something is missing?

should support slack notification for ci build

by using travis-ci settings for dynamic Slack team channel

should make sure the travis-ci build passed

https://travis-ci.org/teracyhq/docker-files/builds/471450235

all the builds should be passed without any error

should have teracy/jp Docker image to be used as pipe with httpie-jwt-auth Docker image

so that we can use with aliases:

$ http | jp for querying the returned JSON data, this is super convenient.

https://github.com/jmespath/jp

Can't seem to get Chrome to start on Circle CI

Whenever I try and run ng test from CircleCI I get the following:

$ ng test ng-fabric-ui --browsers=Chrome_no_sandbox --watch=false --code-coverage
  0% compiling�������������� 10% building 0/0 modules 0 active���������������������������������� 10% building 0/1 modules 1 active ...gular-cli-files/models/jit-polyfills.js� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� ����������������������������������� 10% building 1/1 modules 0 active22 01 2019 22:47:27.674:INFO [karma-server]: Karma v3.1.4 server started at http://0.0.0.0:9876/
22 01 2019 22:47:27.675:INFO [launcher]: Launching browsers Chrome_no_sandbox with concurrency unlimited
22 01 2019 22:47:27.679:INFO [launcher]: Starting browser Chrome
���������������������������������� 10% building 1/2 modules 1 active ...gular-cli-files/models/jit-polyfills.js� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� ����������������������������������� 10% building 2/2 modules 0 active���������������������������������� 10% building 2/3 modules 1 active .../repo/projects/ng-fabric-ui/src/test.ts� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� ����������������������������������� 10% building 3/3 modules 0 active���������������������������������� 10% building 3/4 modules 1 active ...cts/ng-fabric-ui/src sync /\.spec\.ts$/22 01 2019 22:47:27.959:ERROR [launcher]: Cannot start Chrome
	
(google-chrome:145): Gtk-WARNING **: cannot open display: :99.0
[0122/224727.833030:ERROR:nacl_helper_linux.cc(310)] NaCl helper process running without a sandbox!
Most likely you need to configure your SUID sandbox correctly

I have already configured the customLaunchers like so:

customLaunchers: {
  Chrome_no_sandbox: {
    base: 'Chrome',
    flags: ['--no-sandbox', '--disable-setuid-sandbox', '--disable-gpu'] // for running within Docker
  }
}

But still no luck, any help would be appreciated.

jessie-updates moved to archive.debian.org

On March 20, 2019, the Debian project moved the repository jessie-updates to archive.debian.org.

This doesn't have to be part of the base image, but would make it easier:
COPY sources.list /etc/apt/sources.list

[sources.list]:
deb http://deb.debian.org/debian/ jessie main
deb-src http://deb.debian.org/debian/ jessie main

deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main

deb http://archive.debian.org/debian jessie-backports main
deb-src http://archive.debian.org/debian jessie-backports main

And to update apt-get:
apt-get -o Acquire::Check-Valid-Until=false update

should create smaller docker image size of teracy/google-cloud-sdk

the current docker image is too big to be used.

it's better to install on alpine.

should update docs how to use teracy/travis along with teracy/ubuntu for local CI testing

• make sure this works:

vagrant@teracy:~/workspace/docker-files$ docker run --rm -v $(pwd):/tmp -w /tmp hoatle/travis compile > build.sh
detected repository as teracyhq/docker-files
env.matrix key is ignored
vagrant@teracy:~/workspace/docker-files$ docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock -v $(pwd):/$(pwd) -w $(pwd) teracy/ubuntu:16.04-dind-17.06.0-ce bash
root@68388adc3f9e:/home/vagrant/workspace/docker-files# bash build.sh 

it should run the same as on travis-ci (with some exceptions mentioned by travis-build)

And this should help us to update the section Local CI Testing with a real project at http://blog.teracy.com/2017/09/11/how-to-use-docker-in-docker-dind-and-docker-outside-of-docker-dood-for-local-ci-testing/

should add automated tests for Docker images

• https://github.com/sstephenson/bats
• https://github.com/tcnksm-sample/test-driven-development-dockerfile

should create teracy/chefdk that has git installed

this is very useful for us to install dependencies from git repos.

should support completion for aws-cli

make sure this is enabled on the aws-cli docker image, works out of the box when getting into the shell:

$ complete -C '/usr/local/bin/aws_completer' aws

should create different versions of xtrabackup

so that we can use on different projects for backing up/ restoring

should have node-ruby Docker image

so that we could use for some existing projects requiring node and ruby, compass.

should use IMAGE_TAG argument for flexible FROM base image

for example:

FROM python:2.7

to:

ARG IMAGE_TAG=2.7
FROM python:$IMAGE_TAG

Should apply for all the current and future docker files

should create teracy/travis image

that should have https://github.com/travis-ci/travis-build installed so that we can:

• convert .travis.yml to build.sh file for local CI testing (by using teracy/ubuntu image to run this build.sh file)
• use travis client for related tasks

Release a new tag

Hi,

is it possible to release a new tag for angular-cli on DockerHub? the last tag is one year old and using "latest" in pipelines isn't a good practice 😅

Thank you!