Cannot docker build container image #2279
Comments
Also add devel:languages:ruby repository for required ruby2.6 package. Fixes SUSE#2279 Signed-off-by: Josua Mayer <josua@solid-run.com>
|
Hi, branch master and v2.4 is failing. look at the badges. |
Successfully repaired
|
|
oh, just noticed,that's it's your Josua-SR@f297f25 that introduced the updated Ruby installation method, my fix fixes yours... :) full details in release notes of the release I mention at #2241 (comment) |
|
@Jean-Baptiste-Lasselle I am really confused! Besides that, I also have a branch where I can successfully build container images from portus master now ... and I approached it much different apparently: I went on the suse obs and rebuilt the rpms from my fork, and then created the container image from that repo. Your explanations are very extensive and seem to overwhelm me a little. I am especially curious about the ruby versioning issue. I have actually not expected anyone to hardcode the ruby version - not in distro packages - and not in containers. Wouldn't the sane solution be to use system defaults everywhere? |
|
fyi - this is the place: https://build.opensuse.org/project/monitor/home:mayerjosua:branches:Portus |
Hi @Josua-SR Thank you so much for your answer, I have worked to actually understand the whole build from source cycle. So thank you so much for asking me, and for giving me more details on how you, yourself worked on portus.
background_1 | /usr/bin/bundle:23:in `load': cannot load such file -- /usr/lib64/ruby/gems/2.6.0/gems/bundler-1.16.4/exe/bundle (LoadError)
background_1 | from /usr/bin/bundle:23:in `<main>'
zypper ar -f obs://devel:languages:ruby/openSUSE_Leap_15.1 ruby
A few questions on your build from source process
zypper ar -p 1 -f obs://Virtualization:containers:Portus:2.5/openSUSE_Leap_15.1 portus
# --
# And in the original : https://github.com/openSUSE/docker-containers/blob/portus-2.5/derived_images/portus/Dockerfile
# they install [portus] package with :
# zypper ar -p 1 -f obs://Virtualization:containers:Portus:2.5/openSUSE_Leap_15.0 portus
All in all, I would really like to get to the bottom of it all, and fix what I believe is a much higher level issue, like how the whole factory processes are designed. I want to have a factory that completely works, and which people can actually start using in less than one hour of setup, if not 2 minutes, for my customers to trust Also, I am working on deploying to |
|
hi again @Josua-SR , After writing my sum up and questions above, I am almost sure that it is the Portus OpenSUSE package that has a bad design :
BUNDLER_VERSION="1.16.0"And in my fix https://github.com/pokusio/opensuzie-oci-library/releases/tag/0.0.2 , I had to reset bundle version to /usr/bin/gem.ruby2.6 uninstall bundle --version '<1.17.3'
/usr/bin/gem.ruby2.6 install bundle --version '1.16.4'
/usr/bin/gem.ruby2.6 uninstall bundler --version '<1.17.3'
/usr/bin/gem.ruby2.6 install bundler --version '1.16.4'
BUNDLER_VERSION=${BUNDLER_VERSION:-"1.16.0"}
#
# Instead of
# BUNDLER_VERSION="1.16.0"Or it's not worth sharing a file, with an accurate version, if we have to edit it, to use it properly. |
|
I'll try to answer in a structrued way here: This is my current build-process:
There are a few important pieces to note here:
My goals are somewhat related to yours:My use of portus is for an internal docker registry hosting both private and public images - for use by a future CI pipelines. Claire is not something I looked at yet, neither did I deploy more than 1 of portus and background yet. |
I actually believe this bit is irrelevant - the remainder of that script makes no use of this particular variable - or does it? Also, I'd like to point you at my "solution" to bundler, which is inspired by yours, and uses the fact that bundler-1.16.4 is actually part of the portus rpm file: In docker/Dockerfile: |
Nope, not at all. |
Hi @Josua-SR , Thank you so much for this discussion !
About the kiwi fileOmg, I never ever heard or saw reference anywhere in the documentation for https://github.com/openSUSE/portus-image : Thank you so much for telling me about that ! About the strange bundler
I checked it and you are right, I did not check how the variable would be used, checked it now, and there is no executable invoked in the script that can make use of the I am not used to build linux packages yet, but i will soon, I read with interest all this about portus, will be an excellent everyday use case to bear in mind when i'll more work on linux packaging automation.
So there is, a problem somewhere in the CI/CD about dependency management. I'll be very interested in understanding what went wrong then, cause if that happened to an OpenSUSE Team, it is something that will happen to other teams. And hence how that suspicious copy of
Again thank you so much for letting me know about https://github.com/openSUSE/portus-image , and that's very interesting indeed :
That is very interesting, and I will think more about what you wrote, and will continue discuss. https://opensuse.github.io/kiwi/
How interesting, I'll really be interested in somehow keep contact discuss our respective projects development :
# --- CLAIR SCANNER @[clair.pegasusio.io]
# http://port.us.org/features/6_security_scanning.html#intro
# http for test MUST HAVE AN SSL TLS CERTIFICATE
- PORTUS_SECURITY_CLAIR_SERVER=http://clair.pegasusio.io:6060
# - PORTUS_SECURITY_CLAIR_SERVER=https://clair.pegasusio.io:6060
- PORTUS_SECURITY_CLAIR_HEALTH_PORT=6061
- PORTUS_SECURITY_CLAIR_TIMEOUT=900s
clair:
# image: quay.io/coreos/clair:v2.0.1
# image: quay.io/coreos/clair:v2.1.2
# image: ${OCI_REGISTRY_SERVICE_FQDN}/pokus/clair:v2.0.1
image: ${OCI_REGISTRY_SERVICE_FQDN}/pokus/clair:v2.1.2
build:
context: oci/clair
restart: unless-stopped
# entrypoint: ["/usr/bin/dumb-init", "--", "/clair"]
entrypoint: ["/usr/bin/dumb-init", "--", "/clair.customized"]
depends_on:
- postgres
links:
- postgres
ports:
- "6060-6061:6060-6061"
volumes:
- $PWD/tmpclair:/tmp
- $PWD/clair/clair.yml:/clair.yml
# - ./clair/clair.yml:/config/config.yaml
- $PWD/clair/clair.customized:/clair.customized
- $PWD/secrets/certificates:/secrets/certificates
command: [-config, /clair.yml]
networks:
pipeline_portus:
aliases:
- clair.pegasusio.io
postgres:
image: library/postgres:10-alpine
environment:
POSTGRES_PASSWORD: portus
networks:
pipeline_portus:
aliases:
- pgclair.pegasusio.io
FROM quay.io/coreos/clair:v2.1.2
# FROM quay.io/coreos/clair:v2.0.1
# v2.1.2
# see update.sh for why all "apk install"s have to stay as one long line
RUN apk update && apk upgrade && apk add dumb-init curl ca-certificates
RUN chmod +x /clair
COPY clair.customized /
RUN chmod +x /clair.customized
RUN mkdir -p /secrets/certificates
ENTRYPOINT ["/usr/bin/dumb-init", "--", "/clair.customized"]
#!/bin/sh
set -x
echo "--------------------------------"
echo "--------------------------------"
echo "------ [clair.customized] ------"
echo "--------------------------------"
echo "--------------------------------"
mkdir -p /secrets/certificates
echo "--------------------------------"
echo "------ [clair.customized] ------"
echo "------- [ content of ] -------"
echo "-----[/secrets/certificates]----"
echo "--------------------------------"
ls -allh /secrets/certificates
echo "--------------------------------"
cp /secrets/certificates/portus-oci-registry.crt /usr/local/share/ca-certificates
update-ca-certificates
echo "--------------------------------"
echo "------ [clair STARTUP] ------"
echo "--------------------------------"
# passing args from Dockerfile
echo ""
echo "--------------------------------"
echo "------ arg1 = [$1] ------"
echo "--------------------------------"
echo "------ arg2 = [$2] ------"
echo "--------------------------------"
echo ""
/clair $1 $2
# Copyright 2015 clair authors
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# The values specified here are the default values that Clair uses if no configuration file is specified or if the keys are not defined.
clair:
database:
# Database driver
type: pgsql
options:
# PostgreSQL Connection string
# https://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-CONNSTRING
source: host=pgclair.pegasusio.io port=5432 user=postgres password=portus sslmode=disable statement_timeout=60000
# Number of elements kept in the cache
# Values unlikely to change (e.g. namespaces) are cached in order to save prevent needless roundtrips to the database.
cachesize: 16384
# 32-bit URL-safe base64 key used to encrypt pagination tokens
# If one is not provided, it will be generated.
# Multiple clair instances in the same cluster need the same value.
paginationkey:
api:
# v3 grpc/RESTful API server address
addr: "0.0.0.0:6060"
# Health server address
# This is an unencrypted endpoint useful for load balancers to check to healthiness of the clair server.
healthaddr: "0.0.0.0:6061"
# Deadline before an API request will respond with a 503
timeout: 900s
# Optional PKI configuration
# If you want to easily generate client certificates and CAs, try the following projects:
# https://github.com/coreos/etcd-ca
# https://github.com/cloudflare/cfssl
servername:
cafile:
keyfile:
certfile:
worker:
namespace_detectors:
- os-release
- lsb-release
- apt-sources
- alpine-release
- redhat-release
feature_listers:
- apk
- dpkg
- rpm
updater:
# Frequency the database will be updated with vulnerabilities from the default data sources
# The value 0 disables the updater entirely.
interval: 2h
enabledupdaters:
- debian
- ubuntu
- rhel
- oracle
- alpine
notifier:
# Number of attempts before the notification is marked as failed to be sent
attempts: 3
# Duration before a failed notification is retried
renotifyinterval: 2h
http:
# Optional endpoint that will receive notifications via POST requests
endpoint:
# https://PORTUS_SERVICE_FQDN_JINJA2_VAR:3000/v2/token
# Optional PKI configuration
# If you want to easily generate client certificates and CAs, try the following projects:
# https://github.com/cloudflare/cfssl
# https://github.com/coreos/etcd-ca
servername:
cafile:
keyfile:
certfile:
# Optional HTTP Proxy: must be a valid URL (including the scheme).
proxy:
|
Turns out I actually have a little more to say about the Bundler:
With steps 2..5 I completely avoid the initial ruby error about searching a particular version of bundler in |
Thank you so much for clearing that up on the linux packaging side ! This will also be helpful for me to setup a complete rails pipeline, i will for example take in account that no specific version of BUNDLER should be searched, and that's logical here : the version in use should have a symbolic link to the top searched path to bundler binary, which path should both be in path and not mention any version number, for example
I do confirm it is feasible, I have done that just using a
On funny thing to mention here, is that setting up my debian image, I had to use
So I also confirm using I ended up with my modified #!/bin/bash
# --------------------------------------------
# see https://github.com/pokusio/opensuzie-oci-library/issues/1#issuecomment-593322264
# --------------------------------------------
# --------------------------------------------
# ----- POKUS PORTUS FIX
# ----- issue fixed :
# ----- https://github.com/SUSE/Portus/issues/2241
# --------------------------------------------
# --------------------------------------------
# ------ FIX short description
# ---
# --- Goal I had : Do not change the OpenSUSE
# --- package based installation of Portus and
# --- its dependencies, here the Ruby related packages
# --- Because they work hard on packages to be the best suited for the underlying OS.
# ---
# --- I designed the fix based on the closest
# --- issue I found on other ruby stacked
# --- projects on github.com :
# ---
# --- https://github.com/rubygems/rubygems/issues/2180#issuecomment-365263622
# ---
# --- 1./ The issue is that the
# --- OpenSUSE installed package expects
# --- the 'bundle' executable at a path
# --- that does not exist;
# --- So we use a symlink to fix that
# ---
# --- 2./ The issue is that the
# --- OpenSUSE installed package expects
# --- the 'bundle' executable at a path
# --- that does not exist; But I noticed
# --- that this path is using the 'bundle'
# --- executable version number.
# --- So I searched the system, to find
# --- out what version of bundle was installed
# --- by the openSUSE Ruby-packages.
# --- Answer was (dockerhub 'opensuse/portus:2.5')
# --- version '1.16.4'. So I uninstalled the bundle/bundler twins
# ---
# --- Also, paths referenced by the https://github.com/rubygems/rubygems/issues/2180#issuecomment-365263622
# --- were debian specific, so I had to modify
# --- them, to match OpenSUSE Leap file system
# --- layout :
# ---
# --- for example '/usr/lib64/ ...'
# --- instead of '/usr/lib/ ...'
# --- (typical layout customisation for virtualization / containerization)
# --------------------------------------------
# --------------------------------------------
# --------------------------------------------
export RUBY_MAJOR_VERSION=${RUBY_MAJOR_VERSION:-'2'}
export RUBY_MINOR_VERSION=${RUBY_MINOR_VERSION:-'6'}
export RUBY_UPDATE_VERSION=${RUBY_UPDATE_VERSION:-'0'}
export RUBY_VERSION="${RUBY_MAJOR_VERSION}.${RUBY_MINOR_VERSION}.${RUBY_UPDATE_VERSION}"
export RAKE_VERSION=${RAKE_VERSION:-'12.3.2'}
# so GEM_PATH should be set to ... ?
export BUNDLER_VERSION=${BUNDLER_VERSION:-'1.16.4'}
# export RAILS_ENV=production
/usr/bin/gem.ruby2.6 uninstall bundle --version '<1.17.3'
/usr/bin/gem.ruby2.6 install bundle --version '1.16.4'
/usr/bin/gem.ruby2.6 uninstall bundler --version '<1.17.3'
/usr/bin/gem.ruby2.6 install bundler --version '1.16.4'
# ----
# Symlink repairing missing path :
# /usr/lib64/ruby/gems/${RUBY_VERSION}/gems/bundler-${BUNDLER_VERSION}/exe/
#
#
mkdir -p /usr/lib64/ruby/gems/${RUBY_VERSION}/gems/bundler-${BUNDLER_VERSION}/exe/
# because on opensuse Leap_15.1 , the
# ruby bundle executable is at [/usr/bin/bundle.ruby2.6], not at
# [/var/lib/gems/${RUBY_VERSION}/gems ...]
ln -s /usr/bin/bundle.ruby${RUBY_MAJOR_VERSION}.${RUBY_MINOR_VERSION} /usr/lib64/ruby/gems/${RUBY_VERSION}/gems/bundler-${BUNDLER_VERSION}/exe/bundle
ln -s /usr/bin/bundler.ruby${RUBY_MAJOR_VERSION}.${RUBY_MINOR_VERSION} /usr/lib64/ruby/gems/${RUBY_VERSION}/gems/bundler-${BUNDLER_VERSION}/exe/bundler
# ln -s /usr/bin/ruby.ruby${RUBY_MAJOR_VERSION}.${RUBY_MINOR_VERSION} /usr/lib64/ruby/gems/${RUBY_VERSION}/gems/bundler-${BUNDLER_VERSION}/exe/ruby
# ln -s /usr/bin/rake.ruby${RUBY_MAJOR_VERSION}.${RUBY_MINOR_VERSION} /usr/lib64/ruby/gems/${RUBY_VERSION}/gems/bundler-${BUNDLER_VERSION}/exe/rake
# ln -s /usr/bin/gem.ruby${RUBY_MAJOR_VERSION}.${RUBY_MINOR_VERSION} /usr/lib64/ruby/gems/${RUBY_VERSION}/gems/bundler-${BUNDLER_VERSION}/exe/gem
# echo '' > /pokus.portus.issue.2241.fix
# echo 'oui jai bien ete execute tres cher' > /pokus.portus.issue.2241.fix
# echo '' > /pokus.portus.issue.2241.fix
# echo "contenu de []"
# ls -allh /usr/lib64/ruby/gems/${RUBY_VERSION}/gems/rake-${RAKE_VERSION}/exe/rake > /pokus.portus.issue.2241.fix
# echo "répertoire créé : [/usr/lib64/ruby/gems/${RUBY_VERSION}/gems/bundler-${BUNDLER_VERSION}/exe/]" > /pokus.portus.issue.2241.fix
# echo "chemin executable ruby : [/usr/bin/bundle.ruby${RUBY_MAJOR_VERSION}.${RUBY_MINOR_VERSION}]" > /pokus.portus.issue.2241.fix
# echo " [/usr/bin/bundle.ruby${RUBY_MAJOR_VERSION}.${RUBY_MINOR_VERSION}] est mappé sur : [/usr/lib64/ruby/gems/${RUBY_VERSION}/gems/bundler-${BUNDLER_VERSION}/exe/bundle]" > /pokus.portus.issue.2241.fix
# echo "chemin executable ruby : [/usr/bin/bundler.ruby${RUBY_MAJOR_VERSION}.${RUBY_MINOR_VERSION}]" > /pokus.portus.issue.2241.fix
# echo " [/usr/bin/bundler.ruby${RUBY_MAJOR_VERSION}.${RUBY_MINOR_VERSION}] mappé sur : [/usr/lib64/ruby/gems/${RUBY_VERSION}/gems/bundler-${BUNDLER_VERSION}/exe/bundler]" > /pokus.portus.issue.2241.fix
# This script will ensure Portus' database is ready to be used. It will keep
# waiting for the db to be usable, but the script will exit with an error
# after a certain amount of failed attempts.
#
# The script will automatically import all the SSL certificates from
# `/certificates` into the final system. This is needed to talk with the
# registry API when this one is protected by TLS.
#
# Finally the script will start apache running Portus via mod_rails.
set -e
wait_for_database() {
should_setup=${1:-0}
TIMEOUT=90
COUNT=0
RETRY=1
while [ $RETRY -ne 0 ]; do
# case $(portusctl exec --vendor rails r /srv/Portus/bin/check_db.rb | grep DB) in
case $(bundle exec "rails r /srv/Portus/bin/check_db.rb" | grep DB) in
"DB_DOWN")
if [ "$COUNT" -ge "$TIMEOUT" ]; then
printf " [FAIL]\n"
echo "Timeout reached, exiting with error"
exit 1
fi
echo "Waiting for mariadb to be ready in 5 seconds"
sleep 5
COUNT=$((COUNT+5))
;;
"DB_EMPTY"|"DB_MISSING")
if [ $should_setup -eq 1 ]; then
# create db, apply schema and seed
echo "Initializing database"
# portusctl exec --vendor rake db:setup
bundle exec "rake db:setup"
if [ $? -ne 0 ]; then
echo "Error at setup time"
exit 1
fi
fi
;;
"DB_READY")
echo "Database ready"
break
;;
esac
done
set -e
}
setup_database() {
wait_for_database 1
}
# Usage: file_env 'XYZ_DB_PASSWORD' 'example'. This code is taken from:
# https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh
file_env() {
local var="$1"
local fileVar="${var}_FILE"
if [ -v "${var}" ] && [ -v "${fileVar}" ]; then
echo >&2 "error: both $var and $fileVar are set (but are exclusive)"
exit 1
fi
if [ -v "${fileVar}" ]; then
val="$(< "${!fileVar}")"
export "$var"="$val"
fi
unset "$fileVar"
}
# Setup environment variables from secrets.
secrets=( PORTUS_DB_PASSWORD PORTUS_PASSWORD PORTUS_SECRET_KEY_BASE
PORTUS_EMAIL_SMTP_PASSWORD PORTUS_LDAP_AUTHENTICATION_PASSWORD )
for s in "${secrets[@]}"; do
if [[ -z "${!s}" ]]; then
file_env "$s"
fi
done
# Ensure additional certificates (e.g. docker registry) are known.
update-ca-certificates
# Further settings
export PORTUS_PUMA_HOST="0.0.0.0:3000"
export RACK_ENV="production"
export RAILS_ENV="production"
export CCONFIG_PREFIX="PORTUS"
# --- Don't you! (mess with GEM_PATH)
# if [ -z "$PORTUS_GEM_GLOBAL" ]; then
# export GEM_PATH="/srv/Portus/vendor/bundle/ruby/2.6.0"
# fi
# On debug, print the environment in which we'll call Portus.
if [ "$PORTUS_LOG_LEVEL" == "debug" ]; then
# printenv
env
fi
# Go to the Portus directory and execute the proper command.
cd /srv/Portus
if [ ! -z "$PORTUS_BACKGROUND" ]; then
wait_for_database
# portusctl exec --vendor rails r /srv/Portus/bin/background.rb
bundler exec "rails r /srv/Portus/bin/background.rb"
elif [ -z "$PORTUS_INIT_COMMAND" ]; then
setup_database
# portusctl exec --vendor "pumactl -F /srv/Portus/config/puma.rb start"
bundler exec "pumactl -F /srv/Portus/config/puma.rb start"
else
wait_for_database
# portusctl exec --vendor "$PORTUS_INIT_COMMAND"
bundler exec "$PORTUS_INIT_COMMAND"
fi
# ------
# Pour démarrer portus enmode [portus] :
# [bundler exec "pumactl -F /srv/Portus/config/puma.rb start"]
# [bundler exec "puma -C /srv/Portus/config/puma.rb"]
# [rails server]
# ------------------------------------------
# Pour démarrer portus enmode [background] :
# [bundler exec "rails r /srv/Portus/bin/background.rb"]
#
FROM ruby:2.6.0-stretch
# ------------------------------------------
# Custom Commands that I added, inspired by
# https://github.com/SUSE/Portus/issues/2244#issuecomment-584889394
# ------------------------------------------
# Installs rake, and annotate, missing in
# the SUSE/Portus Dockerfile
# ------------------------------------------
# --- because check_dn_.rb expects, I don't know why yet, a 2.6.0 ruby env.
# FROM ruby:2.6.5-stretch
# https://hub.docker.com/layers/ruby/library/ruby/2.6.5-stretch/images/sha256-159e7e054244af6aa75696a2a5141ccbcd12683e5b143dcb17077809d7d0c87d?context=explore
# FROM opensuse/ruby:2.6
# MAINTAINER is deprecated ...
# MAINTAINER SUSE Containers Team <containers@suse.com>
# I don't rely on opensuse/ruby anymore, in the stead, I rely on
# the official https://hub.docker.com/layers/ruby/library/ruby/
#
ENV COMPOSE=1
# Install the entrypoint of this image.
COPY init /
WORKDIR /srv/Portus
# ------------------------------------------------------v
# --- Ok, At OpenSUSE , they wanted to just install
# --- dependencies from Gemfiles, but I have to modify
# --- it live, so I don't want my changes involved by my
# --- 'gem install' commands, to be wiped out
# ---
# COPY built-portus/Gemfile* ./
COPY built-portus/ .
RUN apt-get update -y && apt-get install -y curl
# 1./ Install latest go version : picked from suse team dockerfile : [GOLANG_VERSION=1.10]
ARG GOLANG_VERSION=1.10
ARG GOLANG_OS=linux
ARG GOLANG_CPU_ARCH=amd64
# installing golang version
RUN curl https://dl.google.com/go/go${GOLANG_VERSION}.${GOLANG_OS}-${GOLANG_CPU_ARCH}.tar.gz -o go${GOLANG_VERSION}.${GOLANG_OS}-${GOLANG_CPU_ARCH}.tar.gz
RUN tar -C /usr/local -xzf go${GOLANG_VERSION}.${GOLANG_OS}-${GOLANG_CPU_ARCH}.tar.gz
# ARG PATH=$PATH:/usr/local/go/bin
# ENV PATH=$PATH:/usr/local/go/bin
# ARG PATH
# ENV PATH=$PATH
# RUN export PATH=$PATH:/usr/local/go/bin && go version
RUN PATH=$PATH:/usr/local/go/bin go version
RUN echo "[FINISHED] : Golang installation commands transposed from OPENSUSE to Debian"
# 2./ Then we install dev. dependencies
#
# ------------------------------------------
# ------------------------------------------
# OPENSUSE packages installed using zypper
# ------------------------------------------
# OPENSUSE | DEBIAN
# ------------------------------------------
# ruby2.6-devel | already installed in base image [ruby:2.6.5-stretch]
# libmariadb-devel | libmariadb-dev
# postgresql-devel | postgresql-server-dev-all
# nodejs | [nodejs] Instead of just installing the package ... I install nodejs properly ?
# libxml2-devel | libxml2-dev
# libxslt1 | libxslt1.1
# git-core | git-core
# go1.10 | I don't install that package, I installed a proper golang envrionnement in the stead, no OS package. See section above this table.
# phantomjs | phantomjs
# gcc-c++ | g++, but I installed [build-essential], instead of [g++ / pattern / devel_basis OpenSUSE packages ]
# pattern | ...no match found
# devel_basis | ...no match found
# ------------------------------------------
# Notes on installed packages
# ---> the [devel_basis] [pattern] packages
# are used for building stuff like
# nokogiri.(Source : OpenSUSE Team)
# ------------------------------------------
RUN apt-get install -y libmariadb-dev \
postgresql-server-dev-all \
nodejs \
libxml2-dev \
libxslt1.1 \
git-core \
phantomjs \
build-essential
RUN echo "[FINISHED] : packages installation commands transposed from OPENSUSE to Debian"
# ARG GEM_PATH="/usr/local:/usr/local/bin:/srv/Portus/vendor:/srv/Portus/vendor/bundle:/srv/Portus/vendor/bundle/ruby/2.6.0"
# ENV GEM_PATH="/usr/local:/usr/local/bin:/srv/Portus/vendor:/srv/Portus/vendor/bundle:/srv/Portus/vendor/bundle/ruby/2.6.0"
# ENV GEM_PATH="${GEM_PATH}:/srv/Portus/vendor/bundle/ruby/2.6.0"
# ARG GEM_HOME=/srv/Portus/vendor/bundle/ruby/2.6.0
# ENV GEM_HOME=/srv/Portus/vendor/bundle/ruby/2.6.0
# ENV GEM_HOME=/srv/Portus/vendor/bundle
# https://bundler.io/v1.17/bundle_install.html
# ARG BUNDLE_PATH="${BUNDLE_PATH}:/srv/Portus/vendor/bundle"
# ENV BUNDLE_PATH="${BUNDLE_PATH}:/srv/Portus/vendor/bundle"
# ARG BUNDLE_HOME=/srv/Portus/vendor/bundle
# ENV BUNDLE_HOME=/srv/Portus/vendor/bundle
# ARG RAILS_ENV=prod
# ENV RAILS_ENV=prod
# ------------------------------------------
# Commands that should run identically on
# Debian, and OPENSUSE
# ------------------------------------------
# installs dev stack to build portus
ARG RUBYGEMS_VERSION=3.0.3
ENV RUBYGEMS_VERSION=3.0.3
ARG RAILS_VERSION=5.2.3
ENV RAILS_VERSION=5.2.3
ARG BUNDLE_VERSION='1.16.4'
ENV BUNDLE_VERSION='1.16.4'
ARG BUNDLER_VERSION='1.16.4'
ENV BUNDLER_VERSION='1.16.4'
# -- forcing update rubygem to an accurate version
RUN gem update --system ${RUBYGEMS_VERSION}
# RUN rm /usr/local/bin/bundle
RUN gem uninstall bundler
RUN gem uninstall bundle
RUN gem uninstall bundle --install-dir /usr/local/
RUN rm -fr /usr/local/bundle
# --- #
# RUN gem install bundler --no-document -v 1.17.3
RUN gem update
RUN gem install bundler -v "${BUNDLER_VERSION}"
# RUN gem install bundle --no-document -v "${BUNDLER_VERSION}"
RUN gem install bundle
RUN bundle install --retry=3
# RUN bundle update --bundler
# unnecessary in a docker library official ruby image # update-alternatives --install /usr/bin/bundle bundle /usr/bin/bundle.ruby2.6 3 && \
# unnecessary in a docker library official ruby image # update-alternatives --install /usr/bin/bundler bundler /usr/bin/bundler.ruby2.6 3 && \
RUN export PATH=$PATH:/usr/local/go/bin && go get -u github.com/vbatts/git-validation && \
go get -u github.com/openSUSE/portusctl && \
mv /root/go/bin/git-validation /usr/local/bin/ && \
mv /root/go/bin/portusctl /usr/local/bin/
RUN echo "[FINISHED] : Commands that should run identically on Debian and OEPNSUSE"
# --- mandatory future change :
# accurate version of annotate, no context dependent dependency resolution
ARG RUBY_ANNOTATE_VERSION=3.1.0
ENV RUBY_ANNOTATE_VERSION=3.1.0
# RUBY_ANNOTATE_VERSION=2.7.4
# RUN gem i annotate -v $RUBY_ANNOTATE_VERSION
RUN gem i annotate
ARG RUBY_RAKE_VERSION=12.3.2
ENV RUBY_RAKE_VERSION=12.3.2
RUN gem i rake -v $RUBY_RAKE_VERSION
# ---
# Or Ruby ([RVM RubyVersionManager] I believe) is
# going to throw an error
# ---
# https://rvm.io/workflow/projects
RUN ruby --version|awk '{print $2}' > .ruby-version
# ---
# Or Bundler is gonna complain about it missing
# RUN gem i minitest -v 5.11.3
#
#RUN export PATH=$PATH:/usr/local/go/bin && go get gopkg.in/urfave/cli.v1
RUN apt-get update -y && apt-get install -y go-md2man
RUN apt-get install graphviz -y
# RUN export PATH=$PATH:/usr/local/go/bin && make install
# --
# RUN bundler install --deployment && bundler package --all
EXPOSE 3000
# ENTRYPOINT ["/init"]
# --------------------------------------------------------------
# --------------------------------------------------------------
# ------ IMPOSSIBLE D INSTALLER PORTUSCTL, ET
# ------ SON BUILD FROM SOURCE BEUG DANS TOUS LES SENS
# --------------------------------------------------------------
# --------------------------------------------------------------
# ------
ARG PUMA_VERSION=4.3.3
ENV PUMA_VERSION=4.3.3
RUN gem i puma -v "${PUMA_VERSION}"
COPY .portusgitignore .
RUN cp ./.portusgitignore ./.gitignore
RUN git init
RUN git add --all && git commit -m "releasing-2.5.0-rc"
RUN git tag 2.5.0 -m "releasing-2.5.0-rc"
RUN bundle --deployment
# ---
# ---
# By default,its the foreground webapp and Docker auth v2 service, not the background.
# ---
ENV PORTUS_BACKGROUND=${PORTUS_BACKGROUND:-''}
# ------
# Pour démarrer portus enmode [portus] :
# [bundler exec "pumactl -F /srv/Portus/config/puma.rb start"]
# [bundler exec "puma -C /srv/Portus/config/puma.rb"]
# [rails server]
# ------------------------------------------
# Pour démarrer portus enmode [background] :
# [bundler exec "rails r /srv/Portus/bin/background.rb"]
#
# Tres interessant : la commande pumactl c'estpastrouvée, je suis donc obligé, de trouvr un moyen d'installer pumactl
# root@747b24cf1854:/srv/Portus# git tag 2.5.0 -m "releasing-2.5.0-rc"
# root@747b24cf1854:/srv/Portus# bundler exec "pumactl -F /srv/Portus/config/puma.rb start"
# [25681] Puma starting in cluster mode...
# [25681] * Version 3.12.1 (ruby 2.6.0-p0), codename: Llamas in Pajamas
# [25681] * Min threads: 1, max threads: 4
# [25681] * Environment: development
# [25681] * Process workers: 4
# [25681] * Preloading application
# [schema] Selected the schema for mysql
# [WARN] couldn't connect to database. Skipping PublicActivity::Activity#parameters's serialization
# No such file or directory - connect(2) for /srv/Portus/tmp/sockets/puma.sock
# /usr/local/bundle/gems/puma-3.12.1/lib/puma/binder.rb:371:in `initialize'
# /usr/local/bundle/gems/puma-3.12.1/lib/puma/binder.rb:371:in `new'
# /usr/local/bundle/gems/puma-3.12.1/lib/puma/binder.rb:371:in `add_unix_listener'
# /usr/local/bundle/gems/puma-3.12.1/lib/puma/binder.rb:141:in `block in parse'
# /usr/local/bundle/gems/puma-3.12.1/lib/puma/binder.rb:90:in `each'
# /usr/local/bundle/gems/puma-3.12.1/lib/puma/binder.rb:90:in `parse'
# /usr/local/bundle/gems/puma-3.12.1/lib/puma/runner.rb:153:in `load_and_bind'
# /usr/local/bundle/gems/puma-3.12.1/lib/puma/launcher.rb:186:in `run'
# /usr/local/bundle/gems/puma-3.12.1/lib/puma/cli.rb:80:in `run'
# /usr/local/bundle/gems/puma-3.12.1/lib/puma/cluster.rb:412:in `run'
# /usr/local/bundle/gems/puma-3.12.1/lib/puma/control_cli.rb:261:in `start'
# /usr/local/bundle/gems/puma-3.12.1/lib/puma/control_cli.rb:225:in `run'
# /usr/local/bundle/gems/puma-3.12.1/bin/pumactl:8:in `<top (required)>'
# /usr/local/bundle/bin/pumactl:23:in `load'
# /usr/local/bundle/bin/pumactl:23:in `<main>'
# root@747b24cf1854:/srv/Portus# # git tag 2.5.0 -m "releasing-2.5.0-rc"
# root@747b24cf1854:/srv/Portus# # git add --all && git commit -m "releasing-2.5.0-rc"
# root@747b24cf1854:/srv/Portus# gem install portusctl
# ERROR: Could not find a valid gem 'portusctl' (>= 0) in any repository
# ERROR: Possible alternatives: portugal
# root@747b24cf1854:/srv/Portus# ./bin/
# bundle integration/ rake spring
# ci/ rails setup test-integration.sh
# root@747b24cf1854:/srv/Portus# rails server
# => Booting Puma
# => Rails 5.2.3 application starting in development
# => Run `rails server -h` for more startup options
# [schema] Selected the schema for mysql
# [WARN] couldn't connect to database. Skipping PublicActivity::Activity#parameters's serialization
# [25693] Puma starting in cluster mode...
# [25693] * Version 3.12.1 (ruby 2.6.0-p0), codename: Llamas in Pajamas
# [25693] * Min threads: 1, max threads: 4
# [25693] * Environment: development
# [25693] * Process workers: 4
# [25693] * Preloading application
# [25693] * Listening on unix:///srv/Portus/tmp/sockets/puma.sock
# [25693] Use Ctrl-C to stop
# [25693] - Worker 0 (pid: 25703) booted, phase: 0
# [25693] - Worker 1 (pid: 25705) booted, phase: 0
# [25693] - Worker 2 (pid: 25709) booted, phase: 0
# [25693] - Worker 3 (pid: 25717) booted, phase: 0
#
####### environnement exec portus puma
ENV PORTUS_MACHINE_FQDN=${PORTUS_MACHINE_FQDN:-'pegasusio.io'}
ENV PORTUS_PASSWORD=${PORTUS_PASSWORD:-'123123123'}
ENV PORTUS_KEY_PATH=${PORTUS_KEY_PATH:-'/secrets/certificates/portus.key'}
#RACK ENV DOIT ETRE A PRODUCTION POUR QUE CA FONCTIONNE
ENV RACK_ENV=${RACK_ENV:-'production'}
ENV PORTUS_SECRET_KEY_BASE=${PORTUS_SECRET_KEY_BASE:-'lhkjhgjhgjhgjhgjgf638ygjh685'}
ENV CCONFIG_PREFIX=PORTUS
ENV PORTUS_DB_HOST=${PORTUS_DB_HOST:-'db'}
ENV PORTUS_DB_DATABASE=${PORTUS_DB_DATABASE:-'portus_production'}
ENV PORTUS_DB_PASSWORD=${DATABASE_PASSWORD:-'tintin'}
ENV PORTUS_DB_POOL=5
####### instruction de demarrage qui marche
# bundler exec "pumactl -F /srv/Portus/config/puma.rb start"
RUN bundle --deployment
RUN mkdir -p /srv/Portus/tmp/sockets
RUN touch /srv/Portus/tmp/sockets/puma.sock
CMD ["/bin/bash"] |
Oh, and most of all : AT LAAAAAST we have the final word, so it was worth writing it all down "that there is no executable that make use of the Keeps happening all the time I go "wait, wait, so If we put it in proper words, what is happening here is ...." And when I'm finished writing the question, we all have the answer. But that's a classical, still always good to have everyday proof of that. Also,I really worked hard on the Docker iamge of protus, so I was pretty sure, of the 1.16.4 requirement to run the portus application in puma. SO, when I saw Honestly @Josua-SR I am like really so proud of what we achieved together, so obvious in this page how complementary we were. Oups was going happy too fastActually, that the bundler executable is expected in the vendor directory, is one thing,that does not say, why, in this path So I think we don't have the final word yet, nevertheless,you pointed at a part of portusctl code that is particularly ugly : I mean , really not worth invoking portusctl to run bundle commands.
I don't see another possibility : Don't you think it was this spec file , defining the portus zypper package, which pulled the 1.16.x packages... maybe the 15.0 OBS repo references in the spec file... ? That's what means your result, when you say ;
As for my error logs, It was not in So ok about the |
Successful
|
Released portusctl and portus build from source, all in debianhttps://github.com/pokusio/portus-build-from-source/releases/tag/0.0.1 |
|
Hi @Josua-SR I want to confirm you I just today testdd including my debian based build from source of Portus : and it works great. Josua I really think that the OpenSUSE original design using their package managers is really useless, certainly as badly managed as all other things. I hope you will forgive me, if it s you that hey left alone to manage the I don't think it is you, since you had to raise up your own obs account and run your packages pipelines, but still, they might have accepted merge/pulll requests from you. Plus I want to share with you a great result I understood today, on probably one of the most valuable business case, and I think a very good idea I had about it, see #2281 (comment) |
|
Thanks for all your contributions! |
|
I just found Portus. It looked like a great solution for my private registry needs. Tried installing the official version and it bombed. It didn't like Zypper. I use Ubuntu as my host OS. Can you point me to an install that uses apt-get and creates the GUI container for Portus that I can install and use? It seems to be a great tool if I can get it to work. |
|
@stampeder Use the Docker Image |
Description
Building a container image with
docker build dockerfails.Steps to reproduce
git clone https://github.com/SUSE/Portus.gitcd Portusdocker build dockerDeployment information
No deployment
Configuration:
No configuration
Portus version: master (b87d37e)
The text was updated successfully, but these errors were encountered: