-
Notifications
You must be signed in to change notification settings - Fork 29
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 bilding docker image on linux #13
Open
foxzi
wants to merge
289
commits into
Sulverus:master
Choose a base branch
from
tarantool:foxzi/fix_buildonlinux
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Otherwise people have hard time with setting permissions on their lua scripts. Docker doesn't allow to change them after the VOLUME directive.
How to use: tarantool_set_config.lua TARANTOOL_USER_NAME <new user name> tarantool_set_config.lua TARANTOOL_USER_PASSWORD <new password>
e.g. with: tarantool_set_config.lua TARANTOOL_USER_PASSWORD <new password>
Getting this error when attempt to start any application in tarantool 1.6 /usr/local/bin/tarantoolctl: Configuration failed: Incorrect value for option 'vinyl_dir': unexpected option As far as I know there's no vinyl in 1.6 so maybe just remove the option from default config?
Please update tarantool.default for 1.6
bump tarantool-curl version
Due to the long build we decided to create the new images
with Tarantool installed by a packet manager. Not to build
from source like for Alpine linux.
Closes tarantool/infra#100 tarantool/infra#101
Co-authored-by: Sergey Vorontsov <piligrim@rootnix.net>
GOSU version 1.2 fails on start application with error: runtime: failed to create new OS thread (have 2 already; errno=22) Fix #235
* Add info about new images based on Ubuntu 20.04. * Reflect recent changes in package naming. * General proofreading and formatting. Resolve #232 Co-authored-by: Patience Daur <patiencedaur@gmail.com>
* Fix error with env variable TARANTOOL_PROMETHEUS_DEFAULT_METRICS_PORT wich applies metrics rocks for getting metrics for prometheus Fixes #237
- vshard to 0.1.20 version - queue to 1.2.0 version - http to 1.3.0 version - metrics to 0.14.0 version - gis to 1.0.1 version - mysql to 2.1.1 version
* Variable BASE_IMAGE doesn't use in current building images. * In docker files field FROM fixed for all version OS.
* In alpine images used to LUAJIT_ENABLE_GC64 for enable GC64 now just GC64. * In centos and ubuntu images didn't GC64 aplied, fixed. Default value GC64 set in .gitlab.mk to OFF and can be changed to ON, for centos and ubuntu tarantool install from script wich use value GC64 true or false that's why in docker files for ubuntu centos present if clause for changing OFF to false or ON to true. Default value GC64 set in .gitlab.mk to OFF and can be changed, for centos and ubuntu.
* update version files, now posible install various version on ubuntu and centos * fix problem with gosu in centos images on arm64 arch * replace installing tarantool from script
Bump version of tarantool to 2.10.2. Remove old unused version.
* Bump tarantool version to 2.10.4 * Update gperftools version to 2.10
PostgreSQL 9.6 repo has expired and packages `postgresql96-libs` and `postgresql96-devel` are not available anymore. But it looks like we can install them from the standard repo with version 9.2. Not sure that it's important which version is used. So removing irrelevant `postgresql96` stuff and using the standard repo.
- vshard 0.1.20 -> 0.1.22 - experationd 1.1.1 -> 1.3.1 - queue 1.2.0 -> 1.2.2 - http 1.3.0 -> 1.4.0 - memcached 1.0.1 -> 1.1.0 - metrics 0.14.0 -> 0.16.0 - mysql 2.1.1 -> 2.1.3
On Linux the `make` program uses `/bin/sh` instead of `/bin/bash` by default and substring expansion like this `${VER:0:1}` doesn't work. Now it is fixed.
1314b63
to
66c07e2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix problem with building on linux because make use sh instead of bash and some features doesn't compatible with sh.
Remove deprecated parameter of docker build.