Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] v.4.3 docker fails to start with exit code 243

See original GitHub issue

Describe the bug Docker-compose file that ran previous nightly (nightly-2022-06-22) fine, stops immediately on 4.3 with code 243

version: "3.5"

services:
  ytdl_material:
#    image: tzahi12345/youtubedl-material:nightly-2022-06-22
    image: tzahi12345/youtubedl-material:4.3
    container_name: ytdl_material
    environment: 
      ALLOW_CONFIG_MUTATIONS: 'true'
      write_ytdl_config: 'true'
      ytdl_mongodb_connection_string: 'mongodb://ytdl-mongo-db:27017'
      ytdl_use_local_db: 'false'
      ytdl_port: 9998
      UID: 1026
      GID: 100
    volumes:
      - /volume1/docker/youtube-dlm/appdata:/app/appdata
      - /volume1/video/YoutubeAudio:/app/audio
      - /volume1/video/YoutubeDLM/Singles:/app/video
      - /volume1/video/YoutubeDLM:/app/subscriptions
    ports:
      - 9998:9998/tcp
    networks:
      - ytdl
    depends_on:
      - ytdl-mongo-db
    restart: "no"
      
  ytdl-mongo-db:
    image: mongo:4
    container_name: mongo-db
    ports:
      - 27017:27017
    networks:
      - ytdl
    logging:
      driver: "none"
    volumes:
        - /volume1/docker/youtube-dlm/db/:/data/db
    restart: always
    
networks:
  ytdl:
    name: ytdl

Environment

Version 4.3
Docker tag: latest/4.3
Docker tag nightly-2022-06-22 works

From https://github.com/Tzahi12345/YoutubeDL-Material/pull/117 I assume that error code is related to node/npm.

Issue Analytics

State:
Created a year ago
Reactions:2
Comments:41 (19 by maintainers)

Top GitHub Comments

3reactions

pchristodcommented, Jun 28, 2022

Glad I found this, I would like to mention that I have the exact same issue since I pulled 4.3 a few minutes ago. The container doesn’t start with uid/gid like it did with the Nightlies. Unfortunately I need to have uid/gid because access permissions are set this way. Interestingly I have the same setup as @AlexFullmoon Docker running on Synology with BTRFS Volume.

1reaction

Tzahi12345commented, Jul 5, 2022

Alright should be fixed now (works on my end). Image will be updated in an hour or so if someone can test it out! Commit: fc3c179f6a7ae75554d51a15504f14cc389f3dd3

Top Results From Across the Web

I have error with docker-compose (exited with code 243)

I change node version from node:16 to node:16.14.2 It's work for me. FROM node:16.14.2 ARG stage RUN mkdir -p /app WORKDIR /app COPY...

fails to invoke npm when used in run-scripts #1734 - GitHub

When running within a container runtime, npm fails and returns 243 exit code. $ docker run --rm -v $PWD:/app --workdir /app --entrypoint npm ......

c npm install .' returned a non-zero code: 243 - When building ...

I am trying to use the Node Remote Interpreter to debug a Node app in a docker container using the Docker option i.e....

Investigating pod issues | OpenShift Container Platform 4.8

Depending on policy and exit code, Pods are either removed after exiting or retained so that their logs can be accessed. The first...

cannot start docker compose application. reason: exit status 14

I started getting Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl ...