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

"Cassandra 3.0 and later require Java 8u40 or later" error on newer "-jammy" tags #281

Open
onix opened this issue Apr 27, 2024 · 2 comments

Comments

@onix
Copy link

onix commented Apr 27, 2024

Hi,

with the following docker-compose.yaml

version: '3.0'

volumes:
  cassandra-db: { }

networks:
  test-net:
    driver: bridge

services:
  cassandra-app:
    image: cassandra:3.11.17
    container_name: app-cassandra
    ports:
      - "9042:9042"
    volumes:
      - cassandra-db:/var/lib/cassandra
      - ./cassandra/cassandra-311.yaml:/etc/cassandra/cassandra.yaml
    restart: unless-stopped
    networks:
      - test-net

when starting the docker-compose up, getting an error:

app-cassandra    | Cassandra 3.0 and later require Java 8u40 or later.
app-cassandra exited with code 1

faulty tags are 3.11.17, 3.11.16; I figured out that -jammy does not work, because 3.11.16-focal container starts fine (also 3.11.16 used to work earlier, as I understand it now points to -jammy also).

Host system:
Docker version 20.10.7, build f0df350
docker-compose version 1.24.0, build 0aa59064
Ubuntu 16.04, 4.4.0-1168-aws, x86_64

Understand it's old, however still used to work.

Also can not reproduce this on my local dev macbook with Docker Desktop of recent version: all tags work fine.

Any ideas?

@tianon
Copy link
Member

tianon commented Apr 29, 2024

Oh man, I don't think running Jammy containers on 16.04 is gonna be a good time -- you should probably upgrade the host (at the very least, you'll need an aggressively up-to-date Docker, runc, and libseccomp2, likely newer than is available for 16.04 directly).

@tianon
Copy link
Member

tianon commented Apr 29, 2024

To put that another way, I don't know why it's exhibiting with this particular error message, but I think the error message is a red herring and the real issue is seccomp (and if it isn't, it definitely 100% will be if you get past this first error).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants