CB Server Docker image (x86) fails to run on Docker-for-Mac on Apple Silicon

Description

The Golang binaries in ns_server (gozip vbmap goport godu minify gosecrets) are currently built with Go 1.8.5, which hasn't been a supported version for nearly four years. In particular, this is causing an odd situation reported by a user (https://github.com/couchbase/docker/issues/165 ) where our official Docker images won't run in Docker on Mac M1, because the binaries don't meet some Mac requirement even for running in emulation.

We should upgrade to something much newer, ideally Go 1.15 or so.

Components

Affects versions

Fix versions

Labels

Environment

None

Link to Log File, atop/blg, CBCollectInfo, Core dump

None

Release Notes Description

None

blocks

Activity

Show:

Chris Hillery January 31, 2022 at 8:13 PM

You're not wrong - I'll re-close it as "Will Not Fix". The initial bug was legit, but the solution is "use the aarch64 image (once it's available)".

Dave Rigby January 31, 2022 at 7:45 PM

The current bug title doesn’t match the rationale for closing - the x86_64 Linux images still have problems. Either this needs the title changing to refer to aarch64/Linux Docker images, or it needs re-opening.

Chris Hillery January 31, 2022 at 7:33 PM

As confirmed by and others, the newly-created Linux aarch64 Docker image does work OK on M1 Macs. So my initial information here was incorrect, and there is no need to fix anything.

Meni Hillel December 20, 2021 at 11:46 PM

Remove NS_SERVER as it is not clear to me if we need to do something on our end. Please re-add and clarify ask if needed.

Chris Hillery December 17, 2021 at 6:23 AM

Thank you for the comprehensive explanation. As for your conclusion:

I propose this issue is resolved as "Not a Bug / Known Error" or similar; referring back to the Docker documentation about this not being a fully supported configuration.

I agree, if it is true that the Linux aarch64 ns_server binaries (godu, etc) can run in a Docker image on an M1 Mac. Again, my understanding was that this is NOT true; however I'm having trouble finding the source of that information, so it's quite possible I crossed some wires as well. Based on Ming's last comment, it sounds like this may work after all.

I'm assigning to myself to get to a final answer.

Won't Fix
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Is this a Regression?

No

Triage

Untriaged

Story Points

Sprint

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created October 12, 2021 at 6:51 AM
Updated January 31, 2022 at 8:13 PM
Resolved January 31, 2022 at 8:13 PM
Instabug