I tried to deploy with portainer and it works fine. Please make sure to specify volumes like below:

/home/robin/temp/onedev should be changed as a path on your host machine to store OneDev data.

this is the config i set, i have a dedicated writable volume for onedev and it don't work

OneDev currently expects a bind volume.

Even mounting existing volume works at my side. The error message at your side indicates that the container id used to run inspect command is incorrect. OneDev gets this id from HOSTNAME environment variable. Please run below command to diagnose the issue:

1. From portcontainer, check container id of OneDev
2. Login to OneDev container by running docker exec -it <OneDev container id>
3. Run command echo $HOSTNAME to see if this value is abbreviated form of OneDev container id
4. Run command cat /proc/1/cpuset to see if the output contains the correct container id

Also which version of debian are you using? Is cgroups v2 and rootless container is being used?

The container ID

The it output

You're right, they are different. Why ? And so, how to fix this ?

I'm using debian 11, cgroups v2 is support.

I deployed OneDev via portainer on Debian 11, and the host name is actually abbreviated docker container id, which is expected. I am using the default bridge network. What is your network setting?

In a first fresh deploy, the hostname in the container is the same as the container id.

I found why the container id changed : each time i edit the container and redeploy it.

So, each time i will modify or upgrade it will change. Do you have a fix to sync or hostname with container id ?

In addition to check container by hostname, 6.1 will also check container name "onedev" if that fails.

That's perfect, everything works !! THANKS