Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the link to tarantoolctl in README #9

Closed

Conversation

patiencedaur
Copy link

Resolves tarantool#110

Konstantin Nazarov and others added 30 commits May 27, 2016 17:55
Also, tune slab_alloc_arena to tarantool default.
This change will make the entrypoint similar to tarantoolctl.
There is now a way to change settings dynamically:

tarantool_set_config.lua <env var> <value>

e.g.

tarantool_set_config.lua TARANTOOL_SLAB_ALLOC_ARENA 1.2

All things that can be set via env, can be changed this way.

Fixes #4
This prevents reinitialization of database when
old snapshots are removed. Because initial version
used only snaphost '0' for that purpose.
The print() is buffered and is shown out-of-order
when running container in background.
cyrus-sasl is requied to build updated memcached module

Fixes #8
avtikhon and others added 27 commits August 6, 2020 17:31
Setup makefile to be able to build images manually
on local host without gitlab-ci use.
Removed perl installation from build depends as not needed.
Found issue:

  tarantoolctl rocks install ldoc --server=http://rocks.moonscript.org
  Warning: Failed searching manifest: Failed extracting manifest file:
    'unzip -n' program not found. Make sure unzip is installed and is
    available in your PATH (or you may want to edit the 'variables.UNZIP'
    value in file '/usr/local/etc/tarantool/rocks/config-5.1.lua')
  ldoc not found for Lua 5.1.
  ...
  Error: No results matching query were found for Lua 5.1.

To fix it the unzip package tool was added to be installed before rocks
installations.
Decided to use openssl instead of libressl in alpine 3.9 based images
builds, due to all the issues that caused the use of libressl in
previous were resolved when alpine base image was bumped from 3.5 to
3.9 version.
Due to dockerfiles for Alpine 3.9 builds became the same,
it were merged into common file.
Removed installation of tarantool_curl rock from alpine_3.5_1.x
dockerfile. It affected Tarantool tags builds 1.10.[0-3].
Due to the dockerfiles 'alpine_3.5_[1,2].x' became the same w/o any
differences that can change the images builds, gitlab-ci jobs were
moved to use only one of it - 'alpine_3.5_2.x' to clean it up later.
Due to the dockerfile 'alpine_3.5_1.x' became unused, it was removed.
Standalone dockerfile 'alpine_3.5_2.x' renamed to 'alpine_3.5'.
Due to the dockerfiles 'centos_7_[1,2].x' became the same w/o any
differences that can change the images builds, gitlab-ci jobs were
moved to use only one of it - 'centos_7_2.x' to clean it up later.
Due to the dockerfile 'centos_7_1.x' became unused, it was removed.
Standalone dockerfile 'centos_7_2.x' renamed to 'centos_7'.
Added new tags:
1.10.7: 1.10.7-0-g554d439a5
2.3.3: 2.3.3-0-g5be85a37f
2.4.2: 2.4.2-0-gcccd89701
2.5.1: 2.5.1-0-gc2d8c03ee
2.6.0: 2.6.0-0-g47aa4e01e

Bumped branches:
2.3: 2.3.3-1-g43af95e77
2.4: 2.4.2-1-g3f00d29f9

Created branches:
2.5: 2.5.1-1-g635f6e507

Updated stable images:
*1.x: 1.10.7-1-gb93a33ab2
*2.x: 2.4.2-0-gcccd89701
Until a recent discussion we have to update existing docker tag on
Docker Hub if something is fixed in a Dockerfile. Now we reconsidered
the process and decided to never change existing docker tags.

The reason is simple: there should be a way to freeze an image to get
rid of all possible negative impact due to a change.

The discussion is raised by @tsafin. Thank you, Timur!
Found that since alpine 3.8 the package mariadb-client-libs was
changed to mariadb-connector-c-dev, check [1], [2].

[1] - docker-in-aws/docker-in-aws#1
[2] - https://pkgs.alpinelinux.org/contents?file=libmysqlclient.so*&path=&name=&branch=v3.9&repo=main&arch=x86_64
Found that apk installation fails using '--virtual' option. Also found
that there were two different degradations in Alpine 3.9 [1], one of
which really caused the issue [2]. Degradations where fixed in Alpine
3.11 and backported in Alpine 3.10. To fix the issue on the current
Alpine 3.9 was used the workaround - virtual package was named with
additional suffix to have uniq naming.

Closes #120
Closes #169
Closes #189

Co-authored-by: Alexander Turenko <alexander.turenko@tarantool.org>

[1] - #195 (comment)
[2] - https://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/9651
Set to manual build of the old tagged images.

Added new tags with manual builds:
1.10.8: 1.10.8-0-g2f18757b7
2.4.3: 2.4.3-0-g5180d98f1
2.5.2: 2.5.2-1-gf63c43b9a
2.6.1: 2.6.1-0-gcfe0d1a55
2.7.0: 2.7.0-1-g1ad696c09

Bumped branches:
2.3: 2.3.3-2-g7eea3a6cb
2.4: 2.4.3-1-g986fab717
2.5: 2.5.2-1-gf63c43b9a
2.6: 2.6.1-0-gcfe0d1a55

Updated stable images:
*1.x: 1.10.8-1-ge69e13015
*2.x: 2.5.2-0-g05730d326
Added new tags with manual builds:
1.10.9: 1.10.9-0-g720ffdd23
2.5.3: 2.5.3-0-gf93e48013
2.6.2: 2.6.2-0-g34d504d7d
2.7.1: 2.7.1-0-g3ac498c9f
2.8.0: 2.8.0-0-gefc30ccf8

Bumped branches:
2.5: 2.5.3-0-gf93e48013
2.6: 2.6.2-0-g34d504d7d
2.7: 2.7.1-0-g3ac498c9f

Updated stable images:
*1.x: 1.10.9-0-g720ffdd23
*2.x: 2.6.2-0-g34d504d7d
- Added new tags and rolling versions.
- Reorganized tables of versions to make it compact.
- Corrected patterns for stable versions set.
To avoid of issue:
  CMake Error at third_party/luajit/CMakeLists.txt:11 (cmake_minimum_required):
    CMake 3.1 or higher is required.  You are running version 2.8.12.2

added cmake3 package to CentOS image dockerfile build.
Added new tags with manual builds:
1.10.10: 1.10.10-0-gaea7ae77a
2.6.3: 2.6.3-0-gcd487a2c5
2.7.2: 2.7.2-0-g4d8c06890
2.8.1: 2.8.1-0-ge2a1ec0c2
2.9.0: 2.9.0-0-g15bbdab92

Bumped/created branches:
2.6: 2.6.3-0-gcd487a2c5
2.7: 2.7.2-0-g4d8c06890
2.8: 2.8.1-0-ge2a1ec0c2

Updated stable images:
*1.x: 1.10.10-0-gaea7ae77a
*2.x: 2.7.2-0-g4d8c06890
Since 2.10.0-beta1 release tarantool supports ARM architecture.
Support it in the official docker images.

Build command example:
'export TAG=2.10.0-beta1-amd64 && export OS=alpine DIST=3.9 VER=2.10.0-beta1 ARCH=amd64/ && PORT=5200 make -f .gitlab.mk build'

Close tarantool/tarantool#5868
Close tarantool/tarantool#6154
Update releases: 1.10.11, 2.7.3, 2.8.2, 2.10.0-beta1

Have to set ROCKS_INSTALLER in 1.10.11 version
'export TAG=1.10.11 && export OS=alpine DIST=3.9 VER=1.10.11 ROCKS_INSTALLER=luarocks && PORT=5200 make -f .gitlab.mk build
This patch updates the version for each tarantool module to the latest
tag of the module where it's possible.

Also, a build issue was fixed for Centos 7. It was impossible to
download the pgdg-redhat-repo-latest.noarch.rpm package by the link
from the docker file. So the link was updated.

Clases #208
Closes #215
- added new version files for 1.10.12, 2.8.3, 2.10.0-beta2
- updated the corresponding version files to the latest releases
@patiencedaur
Copy link
Author

Sorry, wrong repo.

@Totktonada Totktonada deleted the patiencedaur/fix-tarantoolctl-link branch February 8, 2022 08:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Link in dockerhub docs is broken