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

Error "Can't start logger thread: Operation not permitted" on container startup #92

Closed
MauroOyhanart opened this issue Oct 3, 2023 · 3 comments

Comments

@MauroOyhanart
Copy link

MauroOyhanart commented Oct 3, 2023

When creating container with docker-compose version v2.20.3 and Docker Engine version 19.03.2.
Using image from Docker Official Repository.
And the following being the docker-compose.yml:

version: '3.3'

services:
  memcached:
    image: memcached:latest
    container_name: memcached
    restart: always
    ports:
      - "11211:11211"
    networks:
      - hosting_network
    volumes:
      - ./log:/var/log/memcached.log
    
networks:
  hosting_network:
    name: hosting_network
    driver: bridge

The container will not start, with the following error logs:

user@server:/path/to/memcached_folder$ docker-compose up

[+] Running 1/0
 ✔ Container memcached  Created                                                                 0.0s 
Attaching to memcached
memcached  | Can't start logger thread: Operation not permitted
memcached exited with code 139
memcached exited with code 0

Running on Ubuntu 16.04.6 LTS (xenial).
My guess is, the docker version might be too old?

1st edit: locally, with newer Docker versions, works just fine.

@dfuentes77
Copy link

dfuentes77 commented Oct 4, 2023

yeah, I'm getting these errors in concourse trying to pull the latest alpine version of memcached container:

waiting for docker to come up...
Login Succeeded
Pulling memcached@sha256:535282ea08869aedc9bd20cbd714f07a27019c8b1e3aa64aa7321c96fb747844...
Error response from daemon: missing signature key

Pulling memcached@sha256:535282ea08869aedc9bd20cbd714f07a27019c8b1e3aa64aa7321c96fb747844 (attempt 2 of 3)...
Error response from daemon: missing signature key

Pulling memcached@sha256:535282ea08869aedc9bd20cbd714f07a27019c8b1e3aa64aa7321c96fb747844 (attempt 3 of 3)...
Error response from daemon: missing signature key

Failed to pull image memcached@sha256:535282ea08869aedc9bd20cbd714f07a27019c8b1e3aa64aa7321c96fb747844.

when I pull the same container locally, it pulls fine

$ docker pull --platform linux/amd64  memcached:alpine
alpine: Pulling from library/memcached
Digest: sha256:535282ea08869aedc9bd20cbd714f07a27019c8b1e3aa64aa7321c96fb747844
Status: Image is up to date for memcached:alpine
docker.io/library/memcached:alpine

@dfuentes77
Copy link

I'm still seeing this error on the latest build of memcached tag alpine:
https://hub.docker.com/layers/library/memcached/alpine/images/sha256-2a0d426a0e8842f181936bbe7378fc20b7fad3f02414130c6b7a12ef3ffd8010?context=explore

I don't see any documentation as to why a change would be made to cause this, any breaking change notice, or notice on the docker hub page. Can anyone speak to the cause and official documentation on breaking change?

@yosifkit
Copy link
Member

Any errors running the a memcached container is very likely libseccomp related with the move to Debian Bookworm in #88 (see also docker-library/python#837 (comment)).

Any issues pulling the image is the same as redis/docker-library-redis#381 (comment)

@tianon tianon closed this as completed Dec 5, 2023
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

4 participants