Make it easy for open liberty to run on k8s with read only file system

Open
#447 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, kubernetes, shell
Domain
cloud, devops, infrastructure

Research direction

Start by examining the base image's docker-server.sh and the Dockerfile used to build it, then reproduce the reported symbolic-link and read-only filesystem behavior on Kubernetes or AKS. Clarify whether the goal is to change the image, document docker-server.sh, or provide a working Dockerfile; done should include a verified read-only filesystem sample.

Written by the indexing model from the issue text.

Description

zenhub-dev

want to run the open liberty on the readonly file system on k8s (AKS) , we are facing issues in using the symbolic link..

Also wanted to know whats the real use of docker-server.sh which is there in the base image? is it really needed ?

is there a fully working sample of a Dockerfile which will run on k8s with R/O file system?

Dominant language
Shell
Stars
48
Forks
60
Avg merge
3h 2m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenLiberty/ci.docker

All issues in OpenLiberty/ci.docker

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.