[BUG]

[shaneoreilly]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When starting the docker image, the following error appears in the logs:

/etc/s6-overlay/s6-rc.d/init-adduser/run: line 46: lsiown: command not found

Logs are here:
LOGS-syno-docker-heimdall-20230820.csv

Expected Behavior

The docker image should start.

Steps To Reproduce

The the docker image (latest)

Environment

- OS: Synology
- How docker service was installed: Native Synology 'Container Manager' tool

CPU architecture

x86-64

Docker creation

Screenshot in comment

Container logs

N/A

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[shaneoreilly]

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[Airwolf1544]

Same Problem here.. just updated from a 3 Year old Image to latest.. exactle the same issue.
Also a Synolog NAS.

[j0nnymoe]

"Bug" is caused by the Synology gui : https://info.linuxserver.io/issues/2023-05-22-portainer/

[drizuid]

Please ensure you guys are deploying your containers in a supported manner, which is docker compose or docker run. We do not support deploying a container from any UI.

Also, container logs being noted as N/A by the OP is not acceptable, they are very applicable, especially when seeking support.

[Airwolf1544]

Hi,
believe in me... nobody reads, what environments are supported ;-)
I can understand, it's frustrating to get bugs reported, which are bugs from other partys..
Everyone get's first to the Software Builder and asks for help.. and if the problem is not there, you search in your (Docker)Environment.. :-)
Anyway.. thank you for help j0nnymoe!

Btw: It's no bad opening post.. everything is there what needed. I'm a sysadmin in an IT Company.. even IT People open tickets, where half of the needed info is missing..

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[Tieske]

To get around this, create a new container. Remove the old one.

Synology;

• select the container
• "action" -> "duplicate settings", give it a new name
• stop and delete the existing container
• start the newly duplicated one

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue is locked due to inactivity