docker-debian-artifacts | Official builds of debuerreotype-generated Debian tarballs | Continuous Deployment library

 by   debuerreotype Shell Version: Current License: Apache-2.0

kandi X-RAY | docker-debian-artifacts Summary

kandi X-RAY | docker-debian-artifacts Summary

docker-debian-artifacts is a Shell library typically used in Devops, Continuous Deployment, Docker, Debian applications. docker-debian-artifacts has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Official builds of debuerreotype-generated Debian tarballs for use in Docker
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              docker-debian-artifacts has a low active ecosystem.
              It has 247 star(s) with 84 fork(s). There are 20 watchers for this library.
              OutlinedDot
              It had no major release in the last 6 months.
              There are 5 open issues and 182 have been closed. On average issues are closed in 23 days. There are 1 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of docker-debian-artifacts is current.

            kandi-Quality Quality

              docker-debian-artifacts has no bugs reported.

            kandi-Security Security

              docker-debian-artifacts has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

            kandi-License License

              docker-debian-artifacts is licensed under the Apache-2.0 License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              docker-debian-artifacts releases are not available. You will need to build from source code and install.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of docker-debian-artifacts
            Get all kandi verified functions for this library.

            docker-debian-artifacts Key Features

            No Key Features are available at this moment for docker-debian-artifacts.

            docker-debian-artifacts Examples and Code Snippets

            No Code Snippets are available at this moment for docker-debian-artifacts.

            Community Discussions

            Trending Discussions on docker-debian-artifacts

            QUESTION

            Docker Images and OS security updates
            Asked 2018-Aug-03 at 12:14

            Let's consider I'm using the Node.js 10.8.0 node:10.8.0-jessie Docker image as a base image for my application Dockerfile. The application is running stable in production and is not updated for a while (several months).

            The Node.js 10.8.0 image is based on the buildpack-deps:jessie image, which itself is based on buildpack-deps:jessie-scm image. This is based on the buildpack-deps:jessie-curl image, whose base image is debian:jessie.

            System / security updates for Debian Jessie are released regularly. In a classic hosted environment I would update my Host using sudo apt-get update && sudo apt-get upgrade and I'm fine.

            But how do I ensure my running Node.js application in the container gets the latest Debian Jessie updates and patches while staying on Node.js node:10.8.0-jessie?

            Running sudo apt-get update && sudo apt-get upgrade for my application Dockerfile in my CI and regularly creating a new Image for my application and re-deploying the container doesn't them the correct way.

            As it all starts with the debian:jessie image, I would expect this to be updated regularly and all depending images as well.

            Then I would rebuild my application image by pulling the Node.js 10.8.0 images again (--no-cache) and re-deploy it.

            My questions are: is this assumption correct? Is there any official Docker documentation about that workflow which seems essential to me? How do I get notified about debian:jessie and eventually node:10.8.0-jessie image patch releases?

            ...

            ANSWER

            Answered 2018-Aug-03 at 12:14

            When I want to use Docker images today, I always try to find the alpine version of this image. There is reasons behind this:

            Alpine Linux is a security-oriented, lightweight Linux distribution based on musl libc and busybox.

            https://alpinelinux.org/

            If you don't know already but you're interested in Alpine Linux, I suggest you to navigate through their website.

            The good point is that this distribution is well handled by a good community. That signifies the distribution is often updated to integrate new security fixes.

            It is important to understand that this is really insteresting (speaking Docker) because, as you said in your question, the built images are immutable through the time.

            By using Alpine based images in Docker, you ensure that you have the latest fix from the actual known bugs/security threats. To know how often they update their Docker image, you can check this page: https://hub.docker.com/r/library/alpine/tags/

            Every image based on this one will be updated at the same time, and there are many image:

            I don't think my solution is the best but it can help anyway:

            On my servers, I created a CRON task that pull every day the Alpine image I'm using, for example node:8-alpine.

            After that, whenever I build my applications based on this image, I'm sure I have the latest updates.

            If you want to go deeper, you can even build you app after pulling the node:8-alpine image.

            For your question about being prevent of new updates/upgrades I don't know how but I you want to use Alpine images you can subscribe to their RSS: https://alpinelinux.org/atom.xml

            There are many others reasons to use Alpine images but since it'll be off topic, I'll just give you this article: https://nickjanetakis.com/blog/the-3-biggest-wins-when-using-alpine-as-a-base-docker-image

            EDIT 1:

            Since you have a CI environment and you build your images with, you can regularly create your own Dockerfile where you do your apt-get update && apt-get install and then use this image as a base images for your application images. But this way will add layers to your final images and then will increase its size.

            Source https://stackoverflow.com/questions/51669697

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install docker-debian-artifacts

            You can download it from GitHub.

            Support

            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/debuerreotype/docker-debian-artifacts.git

          • CLI

            gh repo clone debuerreotype/docker-debian-artifacts

          • sshUrl

            git@github.com:debuerreotype/docker-debian-artifacts.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link