mmul-it / kpa Goto Github PK

KPA - Knowledge Pods Approach

License: MIT License

Jinja 8.63% CSS 9.34% Dockerfile 9.64% Ruby 9.18% TeX 20.32% Shell 42.89%

ansible ansible-playbook ansible-role documentation markdown marp pandoc pdf slides standard knowledge-as-a-service kpa container-image docker

kpa's Issues

Fix Python version to 3.9 inside the kpa container

This will avoid:

Warning: ansible-lint is no longer tested under Python 3.8 and will soon require 3.9. Do not report bugs for this version.

Container build fails (jammy): switch to focal?

Trying to build the kpa container, I get deb signing key errors for the base image:

docker build .         
Sending build context to Docker daemon  9.453MB
Step 1/18 : FROM docker.io/ubuntu:22.04
22.04: Pulling from library/ubuntu
Digest: sha256:dfd64a3b4296d8c9b62aa3309984f8620b98d87e47492599ee20739e8eb54fbf
Status: Downloaded newer image for ubuntu:22.04
 ---> 3b418d7b466a
Step 2/18 : WORKDIR /kpa
 ---> Running in 025f27556ecd
Removing intermediate container 025f27556ecd
 ---> e52e87f3244a
Step 3/18 : RUN apt update
 ---> Running in 0d7cf5ffa18d

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:2 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
Err:1 http://security.ubuntu.com/ubuntu jammy-security InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Err:2 http://archive.ubuntu.com/ubuntu jammy InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [108 kB]
Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Err:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Reading package lists...
W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://security.ubuntu.com/ubuntu jammy-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' is not signed.
W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is not signed.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' is not signed.
E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
E: Sub-process returned an error code
The command '/bin/sh -c apt update' returned a non-zero code: 100

I experienced this with the ubuntu:jammy image in another context, I propose a switch to focal.

Fix paths for pdf generations

Today we rely on an absolute path for kpa_project_dir set to {{ lookup('env', 'PWD') }}/projects/example inside projects/example/common/slides-settings.yml and for marp_output_file set to {{ lookup('env', 'PWD') }}/slides/Example-Training-01.md in the yaml training definition.
Problem is that this complicates how marp-cli inside the container is called when generating pdf, since you need to pass -v $PWD:$PWD to get the same referrals, and this is simply ugly.

Can we remove chrome?

Google chrome is installed in the build container - I'd like to understand where this requirement comes from. Naively it seems like overkill to include a browser in the container, perhaps it's required for pandoc?

Find a way to prevend quay.io to use git cache when generating the KPA container

Even if we tried in every way, it seems impossible to get git clone to always download from the latest commit.
It almost always happens that cache is used and the repository cloned in the container is not up-to-date.
This must be fixed.

Deliver the container to the github container registry

I would like to propose that the kpa container be built during the github actions workflow. Using the token issued to the github action pipeline, we can build and push the container directly to github packages.

Add a release workflow?

Can I propose a release workflow to run a demonstration of how to do CI/CD with Github Actions?

Fix issue with versions in docker images

There are some vulnerabilities on the kpa container image that needs to be fixed, check https://quay.io/repository/mmul/kpa/manifest/sha256:b0cc60e2f268c31cd06889608093b8b7aa121a5efa2025a9ef0196480fcdb9c9?tab=vulnerabilities

Separate test & lint and container build workflows for actions so that they can be triggered separately

Creating two workflow yml files instead of one, we can have kpa_generator trigger just the container build, since there's no big deal in having the lint and test repeated with no code changes and everything should become faster.

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.