Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Scott Mebberson
    @smebberson
    Hey all, welcome to docker-alpine on Gitter. I thought a community around these containers would be great.
    Sandy Trinh
    @sandytrinh
    Hello!
    Hassan Abedi
    @habedi
    Great idea!
    Serge
    @bluetazmanian
    Hi, I have a question in regards to s6-overlay that you use in your Dockerfiles. I use Alpine linux which now has a s6 package writen by Laurent Bercot, would that mean that I do not need to use s6-overlay if its included as a package?
    Scott Mebberson
    @smebberson
    So, the docker-alpine Docker images are all based on Alpine Linux, s6, and s6-overlay. We use s6-overlay because it adds a really nice layer of flexibility for container initialisation, process management and container de-initialisation.
    Using s6 with Alpine Linux is only one part of the process, but designing a more complete *nix init process is more than just using s6 - which is where s6-overlay comes in.
    s6-overlay has not been designed by Laurent Bercot, but he was involved in the process and is consulted very regularly about design decisions. Also, Laurent Bercot has made murmurings about getting more involved with s6-overlay next year with a complete rebuild based on s6-rc.
    @bluetazmanian, I hope that helps you?!
    Jeff Kilbride
    @jeff-kilbride

    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?

    Jeff Kilbride
    @jeff-kilbride
    Somebody in the slack channel helped me out... the docker instance (host) just needed to be restarted.
    sgfgdf
    @sgfgdf_twitter
    hello, guys! i'm trying to install this package https://github.com/sgerrand/alpine-pkg-php5-mongo, but i got this error "ERROR: php5-mongo-1.6.14-r0.apk: IO ERROR". any suggestions?
    KillerSpaz
    @killerspaz
    @sgfgdf_twitter see if this helps gliderlabs/docker-alpine#155
    G. Richard Bellamy
    @rbellamy
    @smebberson ping
    Allan Garcia
    @allangarcia
    Hi, I just want to say GREAT WORK!!! I'll change my actual containers (phusion/baseimage) for this!
    Ruslan
    @disharmonized
    hi guys
    i have question about s6-overlay
    i have container, contains nginx and php-fpm
    i want to collect logs from them
    and i need to be able recognize what is what
    i need to add prefixes in logs for that
    can i do that using s6?
    or i should add prefixes in nginx config and php-fpm config?
    Scott Mebberson
    @smebberson
    @sgfgdf_twitter, did you get your issue sorted?
    Thanks @allangarcia, glad you like them.
    Scott Mebberson
    @smebberson
    @disharmonized, are you using the s6 log functionality, or just standard log functionality from nginx and php-fpm? If so, just add the prefixes as required...
    Orlando Pereira
    @Orpere
    hi