Add build container based on Debian 12 #180
Conversation
…tem-layer into debian12_build_container
|
@ocaisa that change was actually fine, but there's another hardcoded string in the script that prepares the packages... edit: fixed that by doing it in the same way as CVMFS does it here: https://github.com/cvmfs/cvmfs/blob/devel/ci/cvmfs/deb.sh#L36. |
…tem-layer into debian12_build_container
| apt-get install -y wget lsb-release | ||
|
|
||
| arch=$(dpkg --print-architecture) | ||
| os="$(lsb_release -si | tr [:upper:] [:lower:])$(lsb_release -sr)" |
There was a problem hiding this comment.
| os="$(lsb_release -si | tr [:upper:] [:lower:])$(lsb_release -sr)" | |
| os="$(lsb_release -si | tr [:upper:] [:lower:])$(lsb_release -sr | cut -d '.' -f 1)" |
Not sure if this is the problem...
|
|
||
| arch=$(dpkg --print-architecture) | ||
| os="$(lsb_release -si | tr [:upper:] [:lower:])$(lsb_release -sr)" | ||
|
|
||
| if [ "$arch" = "ppc64el" ] || [ "$arch" = "arm64" ] |
There was a problem hiding this comment.
Does it still need to build the deb packages from source for Arm?
There was a problem hiding this comment.
There are packages for Ubuntu, see https://cernvm.cern.ch/fs/, but I'm not sure if they work on Debian.
|
Just tried building a Debian 12 container in my own repo and used that for testing, but it doesn't solve the permission errors with fuse-overlayfs from issue EESSI/software-layer#312. So in that sense we don't really need this, but I can leave it open for now in case we would like to use it. |
No description provided.