Skip to content

Commit

Permalink
Don't call the init process 'init'
Browse files Browse the repository at this point in the history
  • Loading branch information
MinchinWeb committed Apr 20, 2019
1 parent 4c9d601 commit f5e350d
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 0 deletions.
5 changes: 5 additions & 0 deletions Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -31,3 +31,8 @@ ENV COMMIT_SHA=${COMMIT} \
BUILD_DATE=${BUILD_DATE}

COPY root/ /

# having your PID 1 name "init" causes weird Docker bugs; renaming is one fix
# https://github.com/just-containers/s6-overlay/issues/158#issuecomment-266913426
RUN ln -s /init /s6-init
ENTRYPOINT [ "/s6-init" ]
5 changes: 5 additions & 0 deletions Readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,9 @@ space.

- add various tags as per [label-schema.org](http://label-schema.org/rc1/)
- added Canadian English locale, and sets the language to this
- init script is found at `/s6-init`. Turns out naming the process `init`
[causes wierd Docker
bugs](https://github.com/just-containers/s6-overlay/issues/158)

## Prior Art

Expand Down Expand Up @@ -96,3 +99,5 @@ id problem.
- For whatever reason, I couldn't get this image to build locally and work.
However, it works when built on Docker Cloud/Docker Hub.
- Currently, only the "latest" tag (for the Docker image) is supplied.
- `/init` still exists, but don't use it. Use `/s6-init` in stead (see
[here](https://github.com/just-containers/s6-overlay/issues/158))

0 comments on commit f5e350d

Please sign in to comment.