Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: container is unhealthy when changing the WEB_HTTP_PORT environment #276

Open
JinsYin opened this issue Dec 18, 2024 · 1 comment · May be fixed by #275
Open

bug: container is unhealthy when changing the WEB_HTTP_PORT environment #276

JinsYin opened this issue Dec 18, 2024 · 1 comment · May be fixed by #275
Assignees
Labels

Comments

@JinsYin
Copy link

JinsYin commented Dec 18, 2024

Bug Report

When starting the container and changing the WEB_HTTP_PORT environment, the container is unhealthy.

Expected Behavior

The expected state of the container is healthy.

Observed Behavior

The status of the container is healthy: starting.

Steps to Reproduce

Steps to reproduce the behavior:

  1. Run a container:
$ docker run  --rm --name fc \
    -e "WEB_HTTP_PATH=/api" \
    -e "WEB_HTTP_PORT=8080" \
    -e "WEB_HTTP_CATALOG_PORT=8181" \
    -e "WEB_HTTP_CATALOG_PATH=/api/catalog" \
    fc:latest
  1. Check the status of the container:
# health: starting
$ docker ps | grep edc-fc
0604fb2cf681   fc:latest  "sh -c 'exec java $E"   38 seconds ago   Up 37 seconds (health: starting)   8182/tcp fc

Context Information

  • FC: Latest version

Possible Implementation

Modify the HEALTHCHECK instruction of the Dockerfile.

@github-actions github-actions bot added the triage all new issues awaiting classification label Dec 18, 2024
Copy link

Thanks for your contribution 🔥 We will take a look asap 🚀

@JinsYin JinsYin linked a pull request Dec 18, 2024 that will close this issue
@ndr-brt ndr-brt assigned ndr-brt and JinsYin and unassigned ndr-brt Dec 18, 2024
@ndr-brt ndr-brt added build and removed triage all new issues awaiting classification labels Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants