Docker | CentOS | $releasever is “” when running docker build

I am attempting to build a docker image from a CentOS parent image … and installing MongoDB. The error is happening when docker build is adding the MongoDB repo.

You can see that the error is happening because $ releasever is blank for some reason.

DockerFile

FROM centos:latest MAINTAINER "MyName" <myemail@gmail.com> ENV container docker RUN echo -e "\ [mongodb-org-4.0]\n\ name=MongoDB Repository\n\ baseurl=https://repo.mongodb.org/yum/redhat/$  releasever/mongodb-org/4.0/x86_64/\n\ gpgcheck=1\n\ enabled=1\n\ gpgkey=https://www.mongodb.org/static/pgp/server-4.0.asc\n" >> /etc/yum.repos.d/mongodb-org-4.0.repo RUN yum repolist all RUN yum install -y mongodb-org 

ERROR

https://repo.mongodb.org/yum/redhat//mongodb-org/4.0/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found 

rpm build error

Пытаюсь собрать пакет rpm утилиты epm. Deb пакет собирается без проблем. А при сборке rpm выдает ошибку. Собирать пробовал в докере, использовал образа centos6:latest, centos7:latest, centos:latest. Также пробовал на вм centos 7. Везде ошибка зависимости библиотек rpmlib. И ошибка File must begin with “/”

epm -vvvv -f rpm epm --output-dir rpm-distr ESP Package Manager v4.4.1 Copyright 1999-2017 by Michael R Sweet. EPM is free software and comes with ABSOLUTELY NO WARRANTY; for details see the GNU General Public License in the file COPYING or at "http://www.fsf.org/gpl.html".  Report all problems to "https://github.com/michaelrsweet/epm/issues". Searching for product information... Stripping executables in distribution... /usr/bin/strip epm /usr/bin/strip epminstall /usr/bin/strip mkepmlist Creating RPM distribution... Creating spec file... Copying temporary distribution files... epm -> rpm-distr/buildroot/usr/local/bin/epm... epminstall -> rpm-distr/buildroot/usr/local/bin/epminstall... mkepmlist -> rpm-distr/buildroot/usr/local/bin/mkepmlist... ./COPYING -> rpm-distr/buildrootNONE/share/doc/epm/COPYING... ./README.md -> rpm-distr/buildrootNONE/share/doc/epm/README... ./doc/epm-book.html -> rpm-distr/buildrootNONE/share/doc/epm/epm-book.html... ./doc/epm.man -> rpm-distr/buildrootNONE/share/man/man1/epm.1... ./doc/epminstall.man -> rpm-distr/buildrootNONE/share/man/man1/epminstall.1... ./doc/mkepmlist.man -> rpm-distr/buildrootNONE/share/man/man1/mkepmlist.1... ./doc/epm.list.man -> rpm-distr/buildrootNONE/share/man/man5/epm.list.5... Building RPM binary distribution... /usr/bin/rpmbuild -bb --buildroot "/home/devops_cloud19/epm/rpm-distr/buildroot" --target x86_64 rpm-distr/epm.spec Building target platforms: x86_64 Building for target x86_64 Processing files: epm-4.4.1-0.x86_64 Provides: epm = 4.4.1-0 epm(x86-64) = 4.4.1-0 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Processing files: epm-documentation-4.4.1-0.x86_64 error: File must begin with "/": NONE/share/doc/epm/COPYING error: File must begin with "/": NONE/share/doc/epm/README error: File must begin with "/": NONE/share/doc/epm/epm-book.html RPM build errors: File must begin with "/": NONE/share/doc/epm/COPYING File must begin with "/": NONE/share/doc/epm/README File must begin with "/": NONE/share/doc/epm/epm-book.html Packaging failed! 

Archive source folder contents not the folder in azure build pipeline

i am using azure-pipelines to create a build of my react app and then to deploy it to azure app-service now when i build the app all the required contents go it “/build” folder which then i archive and publish to build artifacts with the corresponding tasks. but the issue is in the archive the structure is “/build/{required files}” but i need the structure as “/{required files}” is there any way to achieve it on azure-pipelines.

i have already looked in azure documentation there they show a variable named “includeRootFolder” but even in the link it does not have a description and in the Archive task i am not able to see any option which will set this variable to false.

Build A Basic Messenger Chatbot For Your Business for $50

Are you getting a very low open rate and CTR in your email marketing? Are you tired of getting high cost per lead in your Facebook advertisement? Then you probably need a Facebook Messenger Chatbot Facebook Messenger chatbots are very easy to use and automated that drives the leads at a very low cost. Facebook has over 2 billion users and Messenger has 1.3 billion active users. what’s that mean? Your customer already leveraging the platform, you just need to target them. Who can take the benefit of this Marketing? Any type of service based agency, brand or offline stores. The main benefit of this chatbot is- It’s available 24×7 for your customers, you don’t have to present all the time to your messenger inbox. It increases your response time for the Facebook page. The Work Process: Message me for a free consultationI’ll help you to decide what will be best for your businessI’ll design flow and conversation script for your businessAfter your approval, we’ll set all the flow and launch your chatbotYou can get 30 days Free post-sales support and maintenance. ALERT: This basic package only includes a simple chatbot with upto 10 Interactions and 20 keywords. If you want an advanced one, check out one of my gig “Build An Advanced Messenger Chatbot For Your Business”

by: banhumbleback
Created: —
Category: Other
Viewed: 229


Efficiently sharing a large node_modules directory between multiple TeamCity build jobs

The CI flow for our Node.js app looks roughly like this:


enter image description here


Currently, this all takes place in a single TeamCity ‘job’ with three ‘steps’ (the Test step runs 4 concurrent child processes).

Problems with the current approach:

  • The whole job takes too long – 15 minutes. (The Test subprocesses run in parallel, but this only shaves about 15% compared to running them serially.)
  • The Test step has jumbled log output from 4 child processes, and it’s painful figuring out what failed.

Desired approach

I want to split the above into six TeamCity jobs, using artifact and/or snapshot dependencies to compose them into the desired flow. This should make better use of our pool of four build agents (better parallelism), and it should make failures easier to pinpoint.

But I’m having trouble with sharing the node_modules from the first step so it can be reused by all four jobs in the Test phase. It takes about 3-5 minutes to run yarn (to set up node_modules), so I want to avoid repeating it on every Test job.

Also, most git pushes don’t actually change the npm dependencies, so the ‘Setup’ phase could often be bypassed for speed. CircleCI has a nice way to do this: it lets you cache your node_modules directory with a custom key such as node_modules.<HASH>, using a hash of your lockfile (yarn.lock or package-lock.json) – because the complete node_modules directory is more or less a function of the lockfile.

But my company won’t let me use CircleCI. We have to use TeamCity.

What I’ve tried:

  • Configuring the first TC job to export node_modules as an artifact, but this seems to take forever on TeamCity (>10 minutes for a large node_modules dir), compared to a few seconds on CircleCI. Also, TC doesn’t make it easy to have a dynamic cache key like Circle does.
  • I’ve tried a custom solution: I save a tarball of node_modules to S3 (with cache key based on lockfile), then each Test job streams it down and untars it into node_modules locally, but this ends up taking just as long as running yarn from scratch on each job, so there’s no point.

I’m stuck. Has anyone had any success setting up a CI flow like this on TeamCity?

Which is better build a business on your own or get your friends to invest?

Here's a scenario, you want to build a business but you don't have enough capital to start it on your own. You have friends that can help you in terms of money matters. But the problem is they have no passion or idea on what kind of business you want to build.
Is it better to just load money to get started or ask for your friends to help you with it. Any suggestions on what's the best option to do this?

GPG error – Cannot build openjdk:8-jdk image on ubuntu 16.04

Am trying to create a automated build system with epheremal jenkins slaves as generic build containers


Amidst creation of an image from below Dockerfile:

FROM openjdk:8-jdk    # This is FROM openjdk:8-jdk   RUN apt-get update && apt-get install -y --no-install-recommends \         bzip2 \         unzip \         xz-utils \                 apt-transport-https \     && rm -rf /var/lib/apt/lists/*  RUN echo 'deb http://deb.debian.org/debian jessie-backports main' > /etc/apt/sources.list.d/jessie-backports.list RUN echo 'deb https://apt.dockerproject.org/repo debian-jessie main' > /etc/apt/sources.list.d/docker.list  # Default to UTF-8 file.encoding ENV LANG C.UTF-8  # add a simple script that can auto-detect the appropriate JAVA_HOME value # based on whether the JDK or only the JRE is installed RUN { \         echo '#!/bin/sh'; \         echo 'set -e'; \         echo; \         echo 'dirname "$  (dirname "$  (readlink -f "$  (which javac || which java)")")"'; \     } > /usr/local/bin/docker-java-home \     && chmod +x /usr/local/bin/docker-java-home  ENV JAVA_HOME /usr/lib/jvm/java-8-openjdk-amd64  ENV JAVA_VERSION 8u111 ENV JAVA_DEBIAN_VERSION 8u111-b14-2~bpo8+1  # see https://bugs.debian.org/775775 # and https://github.com/docker-library/java/issues/19#issuecomment-70546872 ENV CA_CERTIFICATES_JAVA_VERSION 20140324  RUN set -x \     && apt-get update \     && apt-get install -y \         openjdk-8-jdk="$  JAVA_DEBIAN_VERSION" \         ca-certificates-java="$  CA_CERTIFICATES_JAVA_VERSION" \     && rm -rf /var/lib/apt/lists/* \     && [ "$  JAVA_HOME" = "$  (docker-java-home)" ] 

After running Step12:

Step 12/24 : RUN set -x     && apt-get update   && apt-get install -y       openjdk-8-jdk="$  JAVA_DEBIAN_VERSION"        ca-certificates-java="$  CA_CERTIFICATES_JAVA_VERSION"    && rm -rf /var/lib/apt/lists/*  && [ "$  JAVA_HOME" = "$  (docker-java-home)" ]  ---> Running in 7d550dcf01b1 + apt-get update 

I get below error:

Ign:1 http://deb.debian.org/debian stretch InRelease Get:2 http://security.debian.org/debian-security stretch/updates InRelease [94.3 kB] Get:3 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB] Ign:4 http://deb.debian.org/debian jessie-backports InRelease Get:5 http://deb.debian.org/debian stretch Release [118 kB] Get:6 https://apt.dockerproject.org/repo debian-jessie InRelease [48.7 kB] Get:7 http://security.debian.org/debian-security stretch/updates/main amd64 Packages [495 kB] Ign:8 http://deb.debian.org/debian jessie-backports Release Ign:6 https://apt.dockerproject.org/repo debian-jessie InRelease Get:9 http://deb.debian.org/debian stretch Release.gpg [2434 B] Get:10 http://deb.debian.org/debian stretch-updates/main amd64 Packages [27.2 kB] Get:11 https://apt.dockerproject.org/repo debian-jessie/main amd64 Packages [6892 B] Ign:12 http://deb.debian.org/debian jessie-backports/main amd64 Packages Ign:13 http://deb.debian.org/debian jessie-backports/main all Packages Get:14 http://deb.debian.org/debian stretch/main amd64 Packages [7082 kB] Ign:12 http://deb.debian.org/debian jessie-backports/main amd64 Packages Ign:13 http://deb.debian.org/debian jessie-backports/main all Packages Ign:12 http://deb.debian.org/debian jessie-backports/main amd64 Packages Ign:13 http://deb.debian.org/debian jessie-backports/main all Packages Ign:12 http://deb.debian.org/debian jessie-backports/main amd64 Packages Ign:13 http://deb.debian.org/debian jessie-backports/main all Packages Ign:12 http://deb.debian.org/debian jessie-backports/main amd64 Packages Ign:13 http://deb.debian.org/debian jessie-backports/main all Packages Err:12 http://deb.debian.org/debian jessie-backports/main amd64 Packages   404  Not Found Ign:13 http://deb.debian.org/debian jessie-backports/main all Packages Fetched 7966 kB in 12s (646 kB/s) Reading package lists... W: The repository 'http://deb.debian.org/debian jessie-backports Release' does not have a Release file. W: GPG error: https://apt.dockerproject.org/repo debian-jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F76221572C52609D W: The repository 'https://apt.dockerproject.org/repo debian-jessie InRelease' is not signed. E: Failed to fetch http://deb.debian.org/debian/dists/jessie-backports/main/binary-amd64/Packages  404  Not Found E: Some index files failed to download. They have been ignored, or old ones used instead. The command '/bin/sh -c set -x  && apt-get update   && apt-get install -y       openjdk-8-jdk="$  JAVA_DEBIAN_VERSION"        ca-certificates-java="$  CA_CERTIFICATES_JAVA_VERSION"    && rm -rf /var/lib/apt/lists/*  && [ "$  JAVA_HOME" = "$  (docker-java-home)" ]' returned a non-zero code: 100