Forward input/output from docker containers to your browser

Startup project. Client side application. Idea is to let people use Linux console directly in the browser. There are Docker containers running under the hood where data is sent to the client via Wesockets. User can type any allowed linux commands to learn Linux or use this app for any other purposes via Linux console.

A full-stack web dashboard for browsing and managing AWS resources running on https://localstack.cloud. Provides an AWS Console-like experience for local development with support for S3, SQS, SNS, IAM, CloudFormation, Lambda, and DynamoDB. Built with Fastify, React, and AWS SDK v3. Available as a web app, docker, standalone

Orchard is a web console to create and manage Linux VMs on macOS using **Virtualization.framework** — no Docker, no QEMU, no Parallels. It exposes a REST API and a browser serial console (xterm.js via WebSocket).

A suite containing biomaj, biomaj-watcher, and all of their dependencies in a docker. Just build, launch, and connect to the IP specified in the console in your browser.

No description available

Console the existing container by using web browser

A small console app for browsing docker registry

A Docker Container that creates a python console in a Web Browser.

Sample code which uses .NET on browser, console or inside docker as WASM

Docker-based mini game console with multiple Python games accessible via browser (noVNC)

Minimal browser tracing demo using OpenTelemetry SDK. Spans are generated on page load and exported to the console. Ready to run locally via Docker Compose.

A full-stack application that fetches and displays Mars rover photos from NASA's API. Features a .NET console app for downloading images and an Angular gallery for browsing the Martian landscape. Includes Docker support and xUnit tests.

▪ For the first container, submit the following: 1. (5 pts) URL for your Docker image that is uploaded to your Docker Hub account (Make sure it’s publicly shared). 2. (5 pts) Screenshot for the execution of your docker container on GCP, showing the “Hello World” message on the console. Your screenshot should show the command you used to run your container on GCP along with the output. Make sure your screenshot includes the cluster name. **If you are unable to combine both in one screenshot, submit one screenshot for the docker command you used on GCP and another screenshot for the output on GCP. 3. (5 pts) Print for your Dockerfile contents and the source code file. ▪ For the second container, submit the following: 1. (5 pts) Screenshot for running Jupyter notebook that is provided from this docker image (i.e. the output of running http://localhost:8888 in your browser).