alpine

Why is crond failing to run a non-root crontab on alpine linux?

非 Y 不嫁゛ 提交于 2019-12-02 01:11:30
问题 I am having a nasty time running a non-root crontab file on Alpine Linux. I've been through two other cron related posts and I don't have an answer: https://askubuntu.com/questions/23009/why-crontab-scripts-are-not-working https://serverfault.com/questions/449651/why-is-my-crontab-not-working-and-how-can-i-troubleshoot-it Here is the setup. My crontab looks like this: PATH=/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/aws/bin:/home/ec2-user/bin SHELL=/bin/bash * * * * *

Why is crond failing to run a non-root crontab on alpine linux?

六眼飞鱼酱① 提交于 2019-12-01 21:18:02
I am having a nasty time running a non-root crontab file on Alpine Linux. I've been through two other cron related posts and I don't have an answer: https://askubuntu.com/questions/23009/why-crontab-scripts-are-not-working https://serverfault.com/questions/449651/why-is-my-crontab-not-working-and-how-can-i-troubleshoot-it Here is the setup. My crontab looks like this: PATH=/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/aws/bin:/home/ec2-user/bin SHELL=/bin/bash * * * * * /opt/monitor/monitor.sh >> /var/log/monitor.log 2>&1 0 3 * * * /opt/monitor/monitor-log-clean.sh >> /var

Oracle on Alpine linux

社会主义新天地 提交于 2019-12-01 17:56:17
I am trying to install OCI8 extension on my Alpine Linux Docker environment. Although there are several places saying it won't work, there are some which say it actually does. I have a 3.4 version and for corporate reasons it is staying like that for now. I have done this within my Docker conf: # Install Oracle Client and build OCI8 (Oracel Command Interface 8 - PHP extension) USER root ENV LD_LIBRARY_PATH=/usr/local/instantclient ENV ORACLE_HOME=/usr/local/instantclient RUN apk update && apk upgrade RUN apk add musl-dev libaio autoconf && apk add --update make ## Unzip Instant Client v12 RUN

Alpine 3.3, Python 2.7.11, urllib2 causing SSL: CERTIFICATE_VERIFY_FAILED

戏子无情 提交于 2019-12-01 16:16:30
I have this small Dockerfile FROM alpine:3.3 RUN apk --update add python CMD ["python", "-c", "import urllib2; response = urllib2.urlopen('https://www.python.org')"] Building it with docker build -t alpine-py/01 . and then running it with docker run -it --rm alpine-py/01 creates the following output Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python2.7/urllib2.py", line 431, in open response = self._open(req, data) File "/usr/lib/python2.7/urllib2.py",

“Server x timed out” during MongoDB aggregation

不羁的心 提交于 2019-12-01 15:28:07
问题 I have a script that periodically runs aggregation on a mongodb collection. As the dataset has grown, the amount of time it takes to aggregate has also grown. My aggregation script has recently stopped working consistently, and the error logs show: error: { [MongoError: server <x> timed out] name: 'MongoError', message: 'server <x> timed out' } I've tried debugging this, and the only pattern I can find is that this timeout seems to only occur when the aggregation takes longer than 2 minutes

add yaml extension to php on using official Alpine Docker image

橙三吉。 提交于 2019-12-01 13:34:33
问题 I'm using this offical php Docker image: https://github.com/docker-library/php/blob/76a1c5ca161f1ed6aafb2c2d26f83ec17360bc68/7.1/alpine/Dockerfile Now I need to add support for yaml extension, that is not bundled with php. I see the base image I'm using uses phpize. I'm trying with this approach: FROM php:7.1.5-alpine # Install and enable yaml extension support to php RUN apk add --update yaml yaml-dev RUN pecl channel-update pecl.php.net RUN pecl install yaml-2.0.0 && docker-php-ext-enable

How to retain docker alpine container after “exit” is used?

血红的双手。 提交于 2019-11-30 20:48:05
Like for example if I use command docker run -it alpine /bin/sh it starts a terminal after which I can install packages and all. Now when I use exit command it goes back to the terminal. (main one) So how can I access the same container again? When I run that command again, I get a fresh alpine. Please help The container lives as long as the specified run command process is still running. When you specify to run /bin/sh , once you exit, the sh process will die and so will you container. If you want to keep your container running, you have to keep the process inside running. For your case (I am

Docker Alpine /bin/sh apk not found

℡╲_俬逩灬. 提交于 2019-11-30 18:21:44
I am building a new Docker image with: FROM alpine:3.4 RUN apk upgrade --update However, its failing with the error: [INFO] /bin/sh: apk: not found This seems to work fine on my local machine (Mac OSX) but when I try building it on a Linux CentOS 7 machine it fails. In the end we upgraded our projects to use this Docker Maven plugin: https://github.com/fabric8io/fabric8-maven-plugin . No issue thus far. I ran into something like this. It completely blew my mind, and I was questioning my sanity for a bit until I realized that /sbin wasn't in my container's path (completely my fault: this was a

How to retain docker alpine container after “exit” is used?

岁酱吖の 提交于 2019-11-30 03:44:17
问题 Like for example if I use command docker run -it alpine /bin/sh it starts a terminal after which I can install packages and all. Now when I use exit command it goes back to the terminal. (main one) So how can I access the same container again? When I run that command again, I get a fresh alpine. Please help 回答1: The container lives as long as the specified run command process is still running. When you specify to run /bin/sh , once you exit, the sh process will die and so will you container.

Docker Alpine /bin/sh apk not found

家住魔仙堡 提交于 2019-11-30 01:50:16
问题 I am building a new Docker image with: FROM alpine:3.4 RUN apk upgrade --update However, its failing with the error: [INFO] /bin/sh: apk: not found This seems to work fine on my local machine (Mac OSX) but when I try building it on a Linux CentOS 7 machine it fails. 回答1: I ran into something like this. It completely blew my mind, and I was questioning my sanity for a bit until I realized that /sbin wasn't in my container's path (completely my fault: this was a change that I made when I was