-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Dear Minos/Mikado developers,
I am trying to use Minos to improve a Braker-derived gene annotation; however, I am having trouble building the Singularity image of Mikado.
(base) [jmartelossi@delta Singularity]$git clone https://github.com/EI-CoreBioinformatics/mikado
(base) [jmartelossi@delta Singularity]$cd mikado/Singularity
(base) [jmartelossi@delta Singularity]$singularity build Singularity.centos.sif Singularity.centos.def
INFO: User not listed in /etc/subuid, trying root-mapped namespace
INFO: The %post section will be run under fakeroot
INFO: Starting build...
Getting image source signatures
Copying blob fab18a2e65e5 skipped: already exists
Copying blob 8ba884070f61 skipped: already exists
Copying config a1dfe42ae9 done
Writing manifest to image destination
Storing signatures
2024/10/01 11:09:04 info unpack layer: sha256:8ba884070f611d31cb2c42eddb691319dc9facf5e0ec67672fcfa135181ab3df
2024/10/01 11:09:06 info unpack layer: sha256:fab18a2e65e55f5d4c10a48e36e0e090345dacd84cf5eb1b6b2526f1a79fe0ad
INFO: Running post scriptlet
+ export PYTHONDONTWRITEBYTECODE=true
+ PYTHONDONTWRITEBYTECODE=true
+ yum -y install git wget zlib1g-dev gcc gcc-c++
Loaded plugins: fastestmirror, ovl
Determining fastest mirrors
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=container error was
14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error"
One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Cannot find a valid baseurl for repo: base/7/x86_64
+ git clone --depth 1 --branch master https://github.com/EI-CoreBioinformatics/mikado.git /usr/local/src/mikado
/.post.script: line 6: git: command not found
FATAL: While performing build: while running engine: exit status 127
Any advice on what is happing here?
The Linux OS I am working on:
NAME="Rocky Linux"
VERSION="8.9 (Green Obsidian)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="8.9"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Rocky Linux 8.9 (Green Obsidian)"
ANSI_COLOR="0;32"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:rocky:rocky:8:GA"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
SUPPORT_END="2029-05-31"
ROCKY_SUPPORT_PRODUCT="Rocky-Linux-8"
ROCKY_SUPPORT_PRODUCT_VERSION="8.9"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.9"
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels