[GH-ISSUE #321] investigate docker vs docker compose regressions #151

New issue

Closed

opened 2026-03-04 01:35:11 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 01:35:11 +03:00

Owner

Originally created by @lts-rad on GitHub (May 8, 2024).
Original GitHub issue: https://github.com/spr-networks/super/issues/321

in the dev branch we have added a :ro workaround for superd mounting the unix socket

"ERROR: for superd Cannot restart container ab0ca33c784337b2186355192bbfa8f75e2bb14e1494cc880928902408d0252b: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/root/super/state/api/eventbus.sock" to rootfs at "/state/api/eventbus.sock": mount /root/super/state/api/eventbus.sock:/state/api/eventbus.sock (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
"

before this we would ocassionally see this error. but we need track down the root cause of this. this was traditionally not an issue for docke rcompose

Originally created by @lts-rad on GitHub (May 8, 2024). Original GitHub issue: https://github.com/spr-networks/super/issues/321 in the dev branch we have added a :ro workaround for superd mounting the unix socket "ERROR: for superd Cannot restart container ab0ca33c784337b2186355192bbfa8f75e2bb14e1494cc880928902408d0252b: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/root/super/state/api/eventbus.sock" to rootfs at "/state/api/eventbus.sock": mount /root/super/state/api/eventbus.sock:/state/api/eventbus.sock (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type " before this we would ocassionally see this error. but we need track down the root cause of this. this was traditionally not an issue for docke rcompose