docker-images - Docker images for Katalon Studio and other frameworks

  •        128

Versions of important packages is written in /katalon/version (or $KATALON_VERSION_FILE). These proxy information will be passed to browsers executing the tests.

https://hub.docker.com/r/katalonstudio
https://github.com/katalon-studio/docker-images

Tags
Implementation
License
Platform

   




Related Projects

docker-selenium - Docker images for Selenium Grid Server (Standalone, Hub, and Nodes).

  •    Dockerfile

The project is made possible by volunteer contributors who have put in thousands of hours of their own time, and made the source code freely available under the Apache License 2.0. ❗️ When executing docker run for an image with Chrome or Firefox please either mount -v /dev/shm:/dev/shm or use the flag --shm-size=2g to use the host's shared memory.

docker-selenium - Selenium in Docker with Chrome & Firefox plus video recording support

  •    Shell

The purpose of this project is to have Selenium running as simple and as fast as possible. This purpose is augmented by Zalenium a project which uses this one to provide docker-selenium(s) on-demand.

selenoid - Selenium Hub successor running browsers within containers

  •    Go

Selenoid is a powerful implementation of Selenium hub using Docker containers to launch browsers. New images are added right after official releases. You can create your custom images with browsers.

docker-chromium-xvfb - Docker image for running browser tests against headless Chromium

  •    Shell

The key to this project and to getting Chromium / Google Chrome to work inside of a container is the wrapper script, xvfb-chromium. The sample application will run the example test and output its results to the console as well as a xunit-format XML file in the test-results/ directory inside of the container.

docker-chromium-xvfb - Docker image for running browser tests against headless Chromium

  •    Dockerfile

The key to this project and to getting Chromium / Google Chrome to work inside of a container is the wrapper script, xvfb-chromium. The sample application will run the example test and output its results to the console as well as a xunit-format XML file in the test-results/ directory inside of the container.


docker-gc - Docker garbage collection of containers and images

  •    Shell

A simple Docker container and image garbage collection script.Although docker normally prevents removal of images that are in use by containers, we take extra care to not remove any image tags (e.g., ubuntu:14.04, busybox, etc) that are in use by containers. A naive docker rmi $(docker images -q) will leave images stripped of all tags, forcing docker to re-pull the repositories when starting new containers even though the images themselves are still on disk.

Harbor - An enterprise-class container registry server based on Docker Distribution

  •    Go

Project Harbor is an enterprise-class registry server that stores and distributes Docker images. It extends the open source Docker Distribution by adding the functionalities usually required by an enterprise, such as security, identity and management. As an enterprise private registry, Harbor offers better performance and security.

aws-lambda-container-image-converter - The AWS Lambda container image converter tool (img2lambda) repackages container images (such as Docker images) into AWS Lambda layers, and publishes them as new layer versions

  •    Go

This container image converter tool (img2lambda) repackages container images (such as Docker images) into AWS Lambda layers, and publishes them as new layer versions to Lambda. The tool copies all files under '/opt' in the Docker image, maintaining the individual Docker image layers as individual Lambda layers. The published layer ARNs will be stored in a file 'output/layers.json', which can be used as input when creating Lambda functions. Each layer is named using a "namespace" prefix (like img2lambda or my-docker-image) and the SHA256 digest of the Docker image layer, in order to provide a way of tracking the provenance of the Lambda layer back to the Docker image that created it.

Packer - Build Automated Machine Images

  •    Go

Packer is a tool for building identical machine images for multiple platforms from a single source configuration. It is lightweight, runs on every major operating system, and is highly performant, creating machine images for multiple platforms in parallel.

Docker-Secure-Deployment-Guidelines - Deployment checklist for securely deploying Docker

  •    

Within today’s growing cloud-based IT market, there is a strong demand for virtualisation technologies. Unfortunately most virtualisation solutions are not flexible enough to meet developer requirements and the overhead implied by the use of full virtualisation solutions becomes a burden on the scalability of the infrastructure. Docker reduces that overhead by allowing developers and system administrators to seamlessly deploy containers for applications and services required for business operations. However, because Docker leverages the same kernel as the host system to reduce the need for resources, containers can be exposed to significant security risks if not adequately configured. The following itemised list suggests hardening actions that can be undertaken to improve the security posture of the containers within their respective environment. It should be noted that proposed solutions only apply to deployment of Linux Docker containers on Linux-based hosts, using the most recent release of Docker at the time of this writing (1.4.0, commit 4595d4f, dating 11/12/14). Part of the content below is based on publications from Jérôme Petazzoni [1] and Daniel J Walsh [2]. This document aims at adding on to their recommendations and how they can specifically be implemented within Docker. Note: Most of suggested command line options can be stored and used in a similar manner inside a Dockerfile for automated image building. Docker 1.3 now supports cryptographic signatures [3] to ascertain the origin and integrity of official repository images. This feature is however still a work in progress as Docker will issue a warning but not prevent the image from actually running. Furthermore, it does not apply to non-official images. In general, ensure that images are only retrieved from trusted repositories and that the --insecure-registry=[] command line option is never used.

source-to-image - A tool for building/building artifacts from source and injecting into docker images

  •    Go

Source-to-Image (S2I) is a toolkit and workflow for building reproducible Docker images from source code. S2I produces ready-to-run images by injecting source code into a Docker container and letting the container prepare that source code for execution. By creating self-assembling builder images, you can version and control your build environments exactly like you use Docker images to version your runtime environments.For a deep dive on S2I you can view this presentation.

whalebrew - Homebrew, but with Docker images

  •    Go

Whalebrew creates aliases for Docker images so you can run them as if they were native commands. It's like Homebrew, but with Docker images. Docker works well for packaging up development environments, but there are lots of tools that aren't tied to a particular project: awscli for managing your AWS account, ffmpeg for converting video, wget for downloading files, and so on. Whalebrew makes those things work with Docker, too.

passenger-docker - Docker base images for Ruby, Python, Node.js and Meteor web apps

  •    Shell

Passenger-docker is a set of Docker images meant to serve as good bases for Ruby, Python, Node.js and Meteor web app images. In line with Phusion Passenger's goal, passenger-docker's goal is to make Docker image building for web apps much easier and faster. Why is this image called "passenger"? It's to represent the ease: you just have to sit back and watch most of the heavy lifting being done for you. Passenger-docker is part of a larger and more ambitious project: to make web app deployment ridiculously simple, to heights never achieved before.

official-images - Docker Official Images

  •    Shell

Work is in-progress in the Docker Engine and Registry to properly support multiple architectures (see docker/docker#15866). While this work is ongoing, temporary, experimental builds of the official images for the following architectures are happening somewhat incrementally (with a strong bias towards images necessary for Docker's own CI to help hasten proper multiarch support upstream) via CI.

ansible-docker-base - Ansible base Images for easy Ansible-Playbook-based Docker builds

  •    

These are base docker images that include Ansible.Ansible, Inc maintains these images so that people can easily build docker images from ansible playbooks.

dotnet-docker - This repo contains the base Docker images for working with

  •    CSharp

Note: .NET Core multi-arch tags, such as 2.0-runtime, have been updated to use nanoserver-1709 images if your host is Windows Server 2016 Version 1709 or higher or Windows 10 Fall Creators Update (Version 1709) or higher. You need Docker 17.10 or later to take advantage of these updated tags.Note: The Docker images in this repo are supported by Microsoft. The arm32v7 images are in preview and have "best effort" support only by the community and .NET Core Team. Please see the arm32 announcement for more details.

PiCluster - Manage Docker Containers

  •    Javascript

PiCluster is a simple way to manage Docker containers on multiple hosts. Docker Swarm not that good and Kubernetes was too difficult to install currently on ARM. PiCluster will only build and run images from Dockerfile's on the host specified in the config file. This software will work on regular x86 hardware also and is not tied to ARM.

sbt-docker - Create Docker images directly from sbt

  •    Scala

sbt-docker is an sbt plugin that builds and pushes Docker images for your project.sbt-docker is an auto plugin, this means that sbt version 0.13.5 or higher is required.

openvas-docker - A Docker container for Openvas

  •    Shell

A Docker container for OpenVAS on Ubuntu. By default, the latest images includes the OpenVAS Base as well as the NVTs and Certs required to run OpenVAS. We made the decision to move to 9 as the default branch since 8 seems to have many issues in docker. We suggest you use 9 as it is much more stable. Our Openvas9 build was designed to be a smaller image with fewer extras built in. Please note, OpenVAS 8 is no longer being built as OpenVAS 9 is now standard. The image is can still be pulled from the Docker hub, however the source has been removed in this github as is standard with deprecated Docker Images. In the output, look for the process scanning cert data. It contains a percentage.