-
Just tested on a new Ubuntu 18 machine, and it works. Please make sure that:
- Property
RUN_AS_USERis specified in bin/agent.sh as the user owning the agent directory - Install agent as root by running
sudo agent.sh install
- Property
-
Hello @robin and thank you for checking this.
Indeed, I've launched fresh Ubuntu 18 KVM, did the same steps and it worked there. The only difference that original Ubuntu 18 is running as LXC container. so it might be related.
Do you have any ideas what can make it unhappy?
-
Never tested on LXC containers. Converted as an improvement request.
-
Name Previous Value Current Value Type
Question
Improvement
-
Previous Value Current Value Ubuntu 18 bare metal agent as service not working
Systemd service support for LXC containers
-
Tested with LXC container and it works at my side. This is what I have done:
-
Start a new EC2 instance with Ubuntu 24.04 image
-
Run below commands to start a LXC container:
sudo apt update sudo apt install -y lxc sudo lxc-create -t download -n test --dist ubuntu --release bionic --arch amd64 sudo lxc-start -n test -
Run
sudo lxc-attach -n testto open a shell to container, and inside the container run below command to start OneDev:apt update apt install -y openjdk-11-jdk wget unzip wget https://code.onedev.io/onedev/server/~site/onedev-latest.zip unzip onedev-latest.zip cd onedev-latest/bin ./server.sh install service onedev start
-
-
Previous Value Current Value Open
Closed
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
Hi,
I'm trying to add an agent on Ubuntu 18 to execute local commands.
I've installed the systemd service by
But when started, it just timeouts
Logs saying its just timed out
I've tried to strace the process and it end loop on this part:
I see no problem connecting agent by using
Need help to sort this, please.