Docker containers running Alpine linux and s6 for process management. Sold, reliable containers.
Glad to find this room! i just pulled the latest alpine:3.4 and rebuilt some containers that depend on it. I'm noticing that the date inside the containers are now off. I've not seen this before. For example:
[2017-01-05 16:14:17]-[jeff@JMBP]-[~]
$ docker run --rm alpine:3.4 date
Thu Jan 5 15:19:54 UTC 2017
The first line is my local system time in PST (Los Angeles, CA). The UTC time reported inside the container is roughly 9 hours off and I'm not sure how to correct it. I'm using docker-alpine
locally for testing several node.js based containers. One of my apps reaches out to Amazon S3 and I'm getting timing errors I've never seen before, e.g.:
RequestTimeTooSkewed: The difference between the request time and the current time is too large.
at extractError (/app/node_modules/aws-sdk/lib/services/s3.js:538:35)
at Request.wrapper (/app/node_modules/@sailshq/lodash/lib/index.js:3250:19)
at Request.callListeners (/app/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
at Request.emit (/app/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
at Request.emit (/app/node_modules/aws-sdk/lib/request.js:668:14)
at Request.transition (/app/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/app/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /app/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request.<anonymous> (/app/node_modules/aws-sdk/lib/request.js:38:9)
at Request.<anonymous> (/app/node_modules/aws-sdk/lib/request.js:670:12)
at Request.callListeners (/app/node_modules/aws-sdk/lib/sequential_executor.js:115:18)
at Request.emit (/app/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
at Request.emit (/app/node_modules/aws-sdk/lib/request.js:668:14)
at Request.transition (/app/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/app/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /app/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request.<anonymous> (/app/node_modules/aws-sdk/lib/request.js:38:9)
at Request.<anonymous> (/app/node_modules/aws-sdk/lib/request.js:670:12)
at Request.callListeners (/app/node_modules/aws-sdk/lib/sequential_executor.js:115:18)
at callNextListener (/app/node_modules/aws-sdk/lib/sequential_executor.js:95:12)
at IncomingMessage.onEnd (/app/node_modules/aws-sdk/lib/event_listeners.js:231:11)
at emitNone (events.js:91:20)
I also pulled alpine:3.5
and I get the same results:
[2017-01-05 16:14:24]-[jeff@JMBP]-[~]
$ docker run --rm alpine:3.5 date
Thu Jan 5 15:20:01 UTC 2017
Anybody have any insight?
/ # ping google.com
ping: bad address 'google.com'
/ # ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=57 time=49.087 ms
64 bytes from 8.8.8.8: seq=1 ttl=57 time=57.769 ms
64 bytes from 8.8.8.8: seq=2 ttl=57 time=55.724 ms
Hi guys! My question is not about docker, but I think you still may help me or at least recommend where I can post the question so it is noticed. I'm trying to install Alpine in PRoot (in order to get it working with no superuser privileges).
Here are the commands:
$ mkdir alpine
$ cp apk.static alpine
$ ./proot -S alpine /apk.static -X http://dl-cdn.alpinelinux.org/alpine/edge/main -U --allow-untrusted --initdb add alpine-base
fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz
(1/16) Installing musl (1.1.16-r15)
(2/16) Installing busybox (1.27.0-r2)
Executing busybox-1.27.0-r2.post-install
ERROR: busybox-1.27.0-r2.post-install: script exited with error 127
(3/16) Installing alpine-baselayout (3.0.4-r0)
Executing alpine-baselayout-3.0.4-r0.pre-install
ERROR: alpine-baselayout-3.0.4-r0.pre-install: script exited with error 127
Executing alpine-baselayout-3.0.4-r0.post-install
ERROR: alpine-baselayout-3.0.4-r0.post-install: script exited with error 127
(4/16) Installing openrc (0.24.1-r2)
Executing openrc-0.24.1-r2.post-install
ERROR: openrc-0.24.1-r2.post-install: script exited with error 127
(5/16) Installing alpine-conf (3.6.0-r0)
(6/16) Installing libressl2.5-libcrypto (2.5.5-r0)
(7/16) Installing libressl2.5-libssl (2.5.5-r0)
(8/16) Installing zlib (1.2.11-r0)
(9/16) Installing apk-tools (2.7.2-r0)
(10/16) Installing busybox-suid (1.27.0-r2)
(11/16) Installing busybox-initscripts (3.1-r1)
Executing busybox-initscripts-3.1-r1.post-install
ERROR: busybox-initscripts-3.1-r1.post-install: script exited with error 127
(12/16) Installing scanelf (1.2.2-r0)
(13/16) Installing musl-utils (1.1.16-r15)
(14/16) Installing libc-utils (0.7.1-r0)
(15/16) Installing alpine-keys (2.1-r1)
(16/16) Installing alpine-base (3.6.0-r0)
Executing busybox-1.27.0-r2.trigger
ERROR: busybox-1.27.0-r2.trigger: script exited with error 127
4 errors; 6 MiB in 16 packages
4 errors in scripts. The scripts look okay and I can run them. I don't know why does it fail. How can I debug the installation? I've been trying rebuilding the packages adding set -x
to the scripts, but I couldn't install my versions because of signature problems. And I doubt that it will help because the scripts probably just fail to run. Is there a simpler way to debug it? It runs okay with root privileges.
I have the following Dockerfile:
`FROM java:8-jdk-alpine
MAINTAINER jemlifathi
RUN apk update && apk --no-cache --update add maven
COPY ./ /home/forms/
WORKDIR /home/forms
RUN mvn clean install
EXPOSE 8080
ENTRYPOINT java -jar ./target/forms-0.0.1.jar`
ERROR: unsatisfiable constraints:
maven (missing):
required by: world[maven]
The command '/bin/sh -c apk update && apk --no-cache --update add maven' returned a non-zero code: 1
docker:stable-dind
, and it seems to have buested our pipeline. Looks like the version of Alpine used installs Node 10.14 while we require 8.14; How can I either revert back to the previous docker image that used the Alpine version which provides that, or pin this node version?