User Guide | Multi-Server | Workspaces | Database |
Kasm Workspaces Container Building
Kasm Workspaces Development
This Kasm workspaces project is intended to produce a Cloud Desktop environment with tools to meet the student’s development needs. Kasm workspaces are dependent on AWS EC2 servers that are installed to support Kasm’s Container streaming technology.
Kasm workspace software development workflow (-> action, * dependency)
---------------------------------------------------------------------
Container Building DockerHub Push Test (via Kasm Container streaming)
|-----------------------| |----------------------| |-----------------------|
| -> Code Docker Image | | -> Publish Images | | -> Install Image |
| Recipes | | with tag | | from Registry |
| * GitHub | | * DockerHub | | -> Start Workspace |
| Code Repo | | Images Repo | | Session |
| | | * GitHub | | -> Test Desktop |
| | | Registry Repo | | Features |
|-----------------------| |----------------------| |-----------------------|
Software Development Life Cycle (SDLC)
--------------------------------------
Code -> Build Docker Images (w/tag) -> Push to DockerHub -> Test Kasm Container
Kasm Workspaces SDLC
The Developer iterates through the actions that follow. Be aware to look ahead as time of jobs, size of images, and tags of images can cause frustrations and challenges.
1. Code
in dockerfile-* and in src directory
- add code for new tools
- add support files to src/ubuntu/install, check [Kasm](https://github.com/kasmtech/workspaces-images.git)
2. Build
the dockerfile-* file
Commands
# clean up docker often, before a new run is best
docker image prune
# tag name needs to match your docker hub setup, see below, latest could be :1.0 for specific verion
docker build -t nighthawkcoders/kasm_workspaces:latest -f dockerfile-csse-nighthawk-ubuntu-jammy-desktop .
Logging
# This can take a long time "20 minutes", see time!!!
[+] Building 872.6s (15/15) FINISHED
=> [internal] load build definition from dockerfile-csse-nighthawk-ubuntu-jammy-desktop-agupta 0.0s
=> => transferring dockerfile: 2.11kB 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/kasmweb/core-ubuntu-focal:1.13.1 2.6s
=> [ 1/10] FROM docker.io/kasmweb/core-ubuntu-focal:1.13.1@sha256:5c2f1bbe9bcc679ddcdf73e21f8ce9d4214cfb 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 15.66kB 0.0s
=> CACHED [ 2/10] WORKDIR /home/kasm-default-profile 0.0s
=> CACHED [ 3/10] COPY ./src/ubuntu/install /dockerstartup/install 0.0s
=> CACHED [ 4/10] RUN for SCRIPT in tools/install_tools.sh chrome/install_chrome.sh 0.0s
=> [ 5/10] RUN cd /tmp/ && wget https://repo.anaconda.com/archive/Anaconda3-2023.07-1-Linux-x86_64 123.9s
=> [ 6/10] RUN echo 'export PATH="/opt/anaconda3/bin:$PATH"' >> /etc/bash.bashrc && /opt/anaconda3 573.9s
=> [ 7/10] RUN chown 1000:0 /home/kasm-default-profile 0.3s
=> [ 8/10] RUN /dockerstartup/set_user_permission.sh /home/kasm-default-profile 1.2s
=> [ 9/10] WORKDIR /home/kasm-user 0.0s
=> [10/10] RUN mkdir -p /home/kasm-user && chown -R 1000:0 /home/kasm-user 0.2s
=> exporting to image 170.3s
=> => exporting layers 170.2s
=> => writing image sha256:d9c1fd0c858f8d6e43eea6d4ce52540e718374da85e8774c05bd2d6f334d374c 0.0s
=> => naming to docker.io/devops/csse-kasm-workspaces:1.0
3. Push
to dockerhub
Commands
# Setup your dockerhub by registering account through docker.io. This is like GitHub, the public repositories are free.
docker login
# if you name is wrong, you can rename it to match: docker tag devops/csse-kasm-workspaces:latest:1.0 nighthawkcoders/kasm_workspaces:latest
# Tag names need to match the [docker hub](https://hub.docker.com/repository/docker/nighthawkcoders/kasm_workspaces/general).
docker push nighthawkcoders/kasm_workspaces:latest
Logging
# This can take a long time "hours if highly customized", but seems to recover from interupts, see log
# Note, screen saver causes job to pause
The push refers to repository [docker.io/nighthawkcoders/kasm_workspaces]
2a1c121ffe10: Preparing
5f70bf18a086: Preparing
ba97dcb9b48e: Preparing
43829d907bf5: Preparing
c2c23b83a67b: Preparing
7394376fd8c2: Waiting
7f71d15b5062: Waiting
8d1ff2660c79: Waiting
d31550a9bd79: Waiting
faf9ed65e452: Waiting
f0e68679b4a0: Waiting
ede4c8fd2a48: Waiting
52bc49669665: Waiting
3ce2f9513d62: Waiting
53c6646e1b86: Waiting
7bb99a4e8d1e: Waiting
980b09195535: Waiting
eaaf9137396d: Waiting
3b294c4eb0b9: Waiting
5cfbbec7fee9: Waiting
7b62ef8b6184: Waiting
d31550a9bd79: Pushing [===============> ] 1.959GB/6.42GB
cf1de89ac5da: Layer already exists
1aed7b7359c3: Layer already exists
91f32011820e: Layer already exists
d9fb259c210b: Layer already exists
f7e680995ade: Layer already exists
0c14e6ac6cf1: Layer already exists
22bef8b22033: Layer already exists
5b8ca191b60b: Layer already exists
2aed46e7ee11: Layer already exists
3f0976fe4ecf: Layer already exists
6eb744c503e9: Layer already exists
4. Test
on Kasm
- Registry setup
- Goto Kasm Sever (aka kasm.nighthawkcodingsociety.com), login admin@kasm.local. Select from the left panel “Workspace”, then “Workspace Registry”. “Add new” registry if “Del Norte HS Computer Science” is not found. Obtain the Registry Link here.
- Click on small icons and install “Available Workspace”. This can take some time!!!
- At the top of the screen select “WORKSPACES” and then install workspace from the registry () is required for the pushed image to be visible on the Kasm workspaces admin panel
- run workplace