Kolab in a docker container

Operating Systems & Open Source Linux
1

So I am trying to set up Kolab in a Docker container.

I want to set up Kolab manually (for educational reasons) and am looking for a lightweight container to do it in. Since the docker search function doesn't show container file sizes, was looking for some help. I would perfer the container to be .deb based

Thanks in advance

-presser

3 Likes
2

I tried looking with google to see what I could find. I could find stuff for install Kolab for Docker not for lightweight container or .deb based.

This guy talks about lightweight containers:
http://blog.librato.com/posts/docker-images

This talks about setting up a docker image:
http://phusion.github.io/baseimage-docker/

This is from 2015 and compares the docker image size:
https://www.brianchristner.io/docker-image-base-os-size-comparison/

Installing docker on Debian:
https://docs.docker.com/engine/installation/linux/debian/

Installing docker on different things:
https://docs.docker.com/engine/installation/

This is Kolab 3.4 Install guide for docker;
https://hub.docker.com/r/kvaps/kolab/

Honestly I don't know if any of this will be helpfully or not. It looks like it could be.

1 Like
3

got an ubuntu image running

trying to learn how to easily save containers locally and then run and attach it

it is like learning a completely new way to do things

1 Like
4

I am interested in this as well. I've only done some preliminary research, so far.

Have you checked around on docker hub? Source code should be on github.

5

From what I've read, CentOS is the native environment for Kolab.

I've been reading up on it for a few weeks now, and it looks like CentOS is your best bet for support and a successful setup.

I don't want to be the first guy to setup Kolab in Ubuntu, even though I hate CentOS/Redhat.

6

I am not so interested in using premade images as I am in taking a basic ubuntu image and building kolab and a lamp stack and then having it saved and running in the back ground.

7

@wendell I wonder if you had some input. My docker knowledge is sadly lacking (im ashamed to say), I know you love containers. Any tips?

8

I am balls deep in the man pages good lord there is so much

9

I'm not sure about docker for one-offs. Maybe? CentOS is maybe good.. Older Kolab worked fine in .deb environments but not sure about the new one. The pre-made images usually have a "step by step" automation thing that does each step for the setup so you can see, for example, a yaml file that does the setup.

1 Like
10

This is why I thought poking around at the source code on github might be worth your time.

11

I got ubuntu running in a container now I am trying to get it to run in the background and attach via tty when I need to admin it.

This is to act a system mail forwarder and a little personal use. Want it to be connected to nextcloud via cardav

12

docker run -d

after I set it up will allow it to run in background not too different than tmux or screen neat

1 Like
13

still having problems keeping dettached containers running they always stop

docker run -d ubuntu /bin/bash

not working grrrrrrrrr

14

bleeding edge.

Warning
Kolab Winterfell eats babies, for breakfast. There is potential data-loss included.

Stick with CentOS. It's their only 'supported' platform.

15

right now I am just trying to figure our how to keep detached containers running

haven't even gotten to kolab yet

16

I'd use buildpack-deps image as a base (its used in a lot of the official images iirc):

https://hub.docker.com/_/buildpack-deps/

You could try to install it on alpine for utra slim images, but I don't recommend it as a first time thing. Debian is going to be pretty slim considering the buildpack one hardly has anything on it.

still having problems keeping dettached containers running they always stop

Try running:

docker run -d --name ubuntu ubuntu:trusty sleep Infinity

and then:

docker exec -ti ubuntu bash

ps. I should probably explain a bit what is going on... Docker is meant to have one process running in its container, once that process exits the container will stop naturally. So as a workaround you can just sleep Infinity and then attach to the container.