lunny/helm-chart
1
0
Fork 0
Code Issues 36 Pull Requests 14 Actions Packages Projects Releases 93 Wiki Activity

memcache: invalid aarch64 image; add nodeSelector #285

New Issue
Closed
opened 2022-01-29 23:32:17 +00:00 by volker.raschek · 8 comments
volker.raschek commented 2022-01-29 23:32:17 +00:00 (Migrated from gitea.com)
Copy Link

Hi,
I added last week an aarch64 node into my cluster. Since the new node has been added and the gitea instance has been rescaled I get some errors with the memcache pod.

It seem's to be, that the memcache chart does not support aarch64, because the deployed pod throws an exec format error.

$ kubectl logs gitea-memcached-864dd9c97f-z5qgn 
exec /opt/bitnami/scripts/memcached/entrypoint.sh: exec format error

Until there is no image for aarch64 should be hardcoded a nodeSelector for arm64 based hosts.

Memcache issue

Hi, I added last week an aarch64 node into my cluster. Since the new node has been added and the gitea instance has been rescaled I get some errors with the memcache pod. It seem's to be, that the memcache chart does not support aarch64, because the deployed pod throws an exec format error. ```bash $ kubectl logs gitea-memcached-864dd9c97f-z5qgn exec /opt/bitnami/scripts/memcached/entrypoint.sh: exec format error ``` Until there is no image for aarch64 should be hardcoded a nodeSelector for arm64 based hosts. [Memcache issue](https://github.com/bitnami/bitnami-docker-memcached/issues/73)
nodesocket commented 2022-03-25 21:57:33 +00:00 (Migrated from gitea.com)
Copy Link

Also trying to run Gitea on a Raspberry Pi k8s cluster and can't use the chart because the dependencies Memcached and PostgreSQL don't support arm64. Are we using the Bitnami charts? Those ALL don't support arm64 and there is a general community outrage about this. Perhaps migrate to using official charts for these dependencies instead of Bitnami?

pi@kube-master:/tmp/gitea $ kubectl logs gitea-memcached-79c5884c97-gmvdg
standard_init_linux.go:228: exec user process caused: exec format error

pi@kube-master:/tmp/gitea $ kubectl logs gitea-postgresql-0
standard_init_linux.go:228: exec user process caused: exec format error
Also trying to run Gitea on a Raspberry Pi k8s cluster and can't use the chart because the dependencies Memcached and PostgreSQL don't support `arm64`. Are we using the Bitnami charts? Those ALL don't support arm64 and there is a general community outrage about this. Perhaps migrate to using official charts for these dependencies instead of Bitnami? ``` pi@kube-master:/tmp/gitea $ kubectl logs gitea-memcached-79c5884c97-gmvdg standard_init_linux.go:228: exec user process caused: exec format error pi@kube-master:/tmp/gitea $ kubectl logs gitea-postgresql-0 standard_init_linux.go:228: exec user process caused: exec format error ```
hwdef commented 2022-11-04 08:18:42 +00:00 (Migrated from gitea.com)
Copy Link

how's the progress

how's the progress
pat-s commented 2023-02-24 09:50:22 +00:00 (Migrated from gitea.com)
Copy Link

Bitnami just announced arm64 images which includes memcached: https://github.com/bitnami/charts/issues/7305#issuecomment-1443187343

But I agree that a nodeSelector would have been nice but given the support now I don't think it's urgently needed anymore.

Make sure to override the memcached image tag yourself as only the most recent images support arm64!

Bitnami just announced arm64 images which includes memcached: https://github.com/bitnami/charts/issues/7305#issuecomment-1443187343 But I agree that a nodeSelector would have been nice but given the support now I don't think it's urgently needed anymore. Make sure to override the memcached image tag yourself as only the most recent images support arm64!
hwdef commented 2023-03-27 07:03:01 +00:00 (Migrated from gitea.com)
Copy Link

image

The software versions used by gitea are very old, and bitnami did not add arm64 versions for these versions of software. we still need to fix this

![image](/attachments/1bb76cb8-24a2-440c-8547-f36c212eeebb) The software versions used by gitea are very old, and bitnami did not add arm64 versions for these versions of software. we still need to fix this
pat-s commented 2023-03-27 07:40:24 +00:00 (Migrated from gitea.com)
Copy Link

A newer version is already in main just not released yet.

A newer version is already in `main` just not released yet.
hwdef commented 2023-03-27 07:44:01 +00:00 (Migrated from gitea.com)
Copy Link

What is the release time?

What is the release time?
pat-s commented 2023-03-28 19:39:19 +00:00 (Migrated from gitea.com)
Copy Link

Apologies, the version was not yet "new" enough.

Apologies, the version was not yet "new" enough.
pat-s commented 2023-03-28 19:39:35 +00:00 (Migrated from gitea.com)
Copy Link

#422 will finally fix it.

#422 will finally fix it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
has/backport
in progress
invalid
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/refactor
kind/security
kind/testing
kind/translation
kind/ui
need/backport
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/other
No Label
kind/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lunny/helm-chart#285
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?