Actions
Idea #9955
closed
keepproxy config file and systemd unit
Added by Peter Amstutz over 8 years ago. Updated over 8 years ago.
Start date:
09/21/2016
Due date:
Story points:
-
Files
| Dockerfile (810 Bytes) Dockerfile | Nico César, 09/28/2016 02:02 PM | ||
| arvados.repo (87 Bytes) arvados.repo | Nico César, 09/28/2016 02:02 PM |
Updated by Tom Morris
Updated by Nico César over 8 years ago
test cef8879203c34fe72725afee259d42bbc0bd5a69
I ran the test locally and the changes seem reasonable.
Updated by Tom Clegg over 8 years ago
- Status changed from In Progress to Resolved
- % Done changed from 50 to 100
Applied in changeset arvados|commit:6de67b677d281b99b53ee9a25c9228523fdf7ee2.
Actions
#6
Updated by Nico César over 8 years ago
- File Dockerfile Dockerfile added
- File arvados.repo arvados.repo added
After some research is possible to run SystemD in docker! (I know, exciting times ahead, so good to be alive, etc. etc)
docker build . docker run --cap-add SYS_ADMIN -t --rm --name server-1 -v /sys/fs/cgroup:/sys/fs/cgroup 1be130b04bad
which I get...
systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
Detected virtualization docker.
Detected architecture x86-64.
Welcome to CentOS Linux 7 (Core)!
Set hostname to <e3a852d4c68b>.
Initializing machine ID from random generator.
Failed to install release agent, ignoring: File exists
Running in a container, ignoring fstab device entry for /dev/disk/by-uuid/4d69694c-cafa-40df-8797-554b40661ab8.
[ OK ] Reached target Swap.
[ OK ] Created slice Root Slice.
[ OK ] Listening on Delayed Shutdown Socket.
[ OK ] Created slice System Slice.
[ OK ] Reached target Paths.
[ OK ] Listening on Journal Socket.
[ OK ] Reached target Local File Systems.
Starting Create Volatile Files and Directories...
[ OK ] Reached target Slices.
Starting Journal Service...
[ OK ] Started Create Volatile Files and Directories.
[ INFO ] Update UTMP about System Boot/Shutdown is not active.
[DEPEND] Dependency failed for Update UTMP about System Runlevel Changes.
Job systemd-update-utmp-runlevel.service/start failed with result 'dependency'.
[ OK ] Started Journal Service.
[ OK ] Reached target System Initialization.
[ OK ] Reached target Timers.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting Arvados Keep Proxy...
Starting Cleanup of Temporary Directories...
[ OK ] Started Cleanup of Temporary Directories.
[FAILED] Failed to start Arvados Keep Proxy.
See 'systemctl status keepproxy.service' for details.
[ OK ] Reached target Multi-User System.
docker exec -ti e3a852d4c68b /bin/bash
[root@e3a852d4c68b /]# systemctl status keepproxy.service
● keepproxy.service - Arvados Keep Proxy
Loaded: loaded (/usr/lib/systemd/system/keepproxy.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Tue 2016-09-27 22:43:17 UTC; 1min 30s ago
Docs: https://doc.arvados.org/
Process: 36 ExecStart=/usr/bin/keepproxy (code=exited, status=1/FAILURE)
Main PID: 36 (code=exited, status=1/FAILURE)
Sep 27 22:43:17 e3a852d4c68b systemd[1]: Failed to start Arvados Keep Proxy.
Sep 27 22:43:17 e3a852d4c68b systemd[1]: Unit keepproxy.service entered failed state.
Sep 27 22:43:17 e3a852d4c68b systemd[1]: keepproxy.service failed.
Sep 27 22:43:17 e3a852d4c68b systemd[1]: keepproxy.service holdoff time over, scheduling restart.
Sep 27 22:43:17 e3a852d4c68b systemd[1]: start request repeated too quickly for keepproxy.service
Sep 27 22:43:17 e3a852d4c68b systemd[1]: Failed to start Arvados Keep Proxy.
Sep 27 22:43:17 e3a852d4c68b systemd[1]: Unit keepproxy.service entered failed state.
Sep 27 22:43:17 e3a852d4c68b systemd[1]: keepproxy.service failed.
[root@e3a852d4c68b /]# journalctl -x
Sep 27 22:43:16 e3a852d4c68b systemd[1]: Starting Arvados Keep Proxy...
-- Subject: Unit keepproxy.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit keepproxy.service has begun starting up.
Sep 27 22:43:16 e3a852d4c68b systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: Unit systemd-tmpfiles-clean.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-clean.service has begun starting up.
Sep 27 22:43:16 e3a852d4c68b systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-tmpfiles-clean.service has finished starting up.
--
-- The start-up result is done.
Sep 27 22:43:16 e3a852d4c68b keepproxy[18]: 2016/09/27 22:43:16 open /etc/arvados/keepproxy/keepproxy.yml: no such file or directory
Sep 27 22:43:16 e3a852d4c68b systemd[1]: keepproxy.service: main process exited, code=exited, status=1/FAILURE
Sep 27 22:43:16 e3a852d4c68b systemd[1]: Failed to start Arvados Keep Proxy.
-- Subject: Unit keepproxy.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit keepproxy.service has failed.
--
-- The result is failed.
Sep 27 22:43:16 e3a852d4c68b systemd[1]: Unit keepproxy.service entered failed state.
Sep 27 22:43:16 e3a852d4c68b systemd[1]: keepproxy.service failed.
Sep 27 22:43:16 e3a852d4c68b systemd[1]: Reached target Multi-User System.
-- Subject: Unit multi-user.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit multi-user.target has finished starting up.
--
-- The start-up result is done.
Actions