#933  Podman support
Closed
Robin Shen opened 2 years ago

$ podman run --name onedev --tty --rm -v $(pwd):/opt/onedev -p 6610:6610 -p 6611:6611 docker.io/1dev/server INFO - Launching application from '/app'... OneDev reports below error when running with podman:

INFO  - Starting server...
ERROR - Error booting application
java.lang.NullPointerException: null
    at io.onedev.server.maintenance.Upgrade.start(Upgrade.java:163)
    at io.onedev.server.OneDev.start(OneDev.java:109)
    at io.onedev.commons.loader.DefaultPluginManager.start(DefaultPluginManager.java:44)
    at io.onedev.commons.loader.AppLoader.start(AppLoader.java:73)
    at io.onedev.commons.bootstrap.Bootstrap.main(Bootstrap.java:189)
Sean McMurray commented 2 years ago

$ podman run --tty --rm -v $XDG_RUNTIME_DIR/podman/podman.sock:/var/run/docker.sock -v $(pwd)/onedev:/opt/onedev -p 6610:6610 -p 6611:6611 1dev/server INFO - Launching application from '/app'... INFO - Starting server... ERROR - Error booting application java.lang.NullPointerException: null at io.onedev.server.maintenance.Upgrade.start(Upgrade.java:172) at io.onedev.server.OneDev.start(OneDev.java:112) at io.onedev.commons.loader.DefaultPluginManager.start(DefaultPluginManager.java:44) at io.onedev.commons.loader.AppLoader.start(AppLoader.java:73) at io.onedev.commons.bootstrap.Bootstrap.main(Bootstrap.java:189)

Robin Shen commented 2 years ago

Please give more details for this error. I tested on Ubuntu 22 with podman 3.4.4, and it reports Error: statfs /run/user/1000/podman/podman.sock: no such file or directory which does not seem like a OneDev issue.

Robin Shen commented 2 years ago

My mistake. After starting podman system service. It works fine. So please let me know your environment. Also please pull onedev image before running this to make sure most recent image is being used.

Robin Shen changed state to 'Closed' 2 years ago
Previous Value Current Value
Open
Closed
issue 1 of 1
Type
Improvement
Priority
Normal
Assignee
Issue Votes (1)
Watchers (3)
Reference
onedev/server#933
Please wait...
Page is in error, reload to recover