+
Skip to content

Optimizing the wekan Dockerfile  #1560

Closed
@gotjoshua

Description

@gotjoshua

I am in the process of dividing and reordering the single jumbo command currently in the wekan Dockerfile to allow for some caching in the build process.

I am making good progress - 23 of 31 steps caching when i change a file in the app
(available for review in my fork: Dockerfile )

I have some questions:

  1. Why is the Alpine Linux "paxctl fix" needed if the container is "FROM debian:buster-slim" ?

  2. Would it be possible to clean up some of the build dependencies earlier in the process - before the actual app build (eg curl and wget once they are not needed anymore) ?

  • I guess the question here is which build dependencies are needed in which stages of the process?
  1. Why are we tracing "meteor -- help;" during build?

Has optimization been considered at all yet?
I am using these resources so far:
https://medium.com/@esotericmeans/optimizing-your-dockerfile-dc4b7b527756

http://bitjudo.com/blog/2014/03/13/building-efficient-dockerfiles-node-dot-js/

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载