Skip to content
This repository has been archived by the owner on Apr 11, 2019. It is now read-only.

limitations when creating docker container installation #10

Open
rcruicks opened this issue Aug 3, 2016 · 1 comment
Open

limitations when creating docker container installation #10

rcruicks opened this issue Aug 3, 2016 · 1 comment

Comments

@rcruicks
Copy link

rcruicks commented Aug 3, 2016

trying to install demo live system in bluemix container environment (docker)

install-system.sh will fail when trying to create and manipulate swap settings -- script option to bypass swapfile section?

install-system.sh will fail trying to install fuse device from openjdk-associated packages -- apt-get install will work if it includes "--no-install-recommends"

hardcoding of database name to openeyes in numerous locations prevents creating mysql database in cloud-managed service (these pre-assign dbname) - container with remote database would require options on install-oe.sh to provide -u -p -h -P and -D overrides

just found that cloud mysql server (in multitenant service) does not allow superuser GRANT privileges with default access account -- ideally would like to set username/password to cloud service credentials

@rcruicks
Copy link
Author

it seems to be able to do swapon/swapoff and mknod operations in docker, host admin privileges are required; this can lead to other problems, and are often made unavailable.
a check for running within a docker container could automate bypass of the failing instructions

if grep "cpu:/docker" /proc/1/cgroup >/dev/null;
then
enable swapfile stuff
enable fuse-related stuff
fi

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant