You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been developing quite a few scenarios recently using Docker Containers.
Mostly I use base Linux containers and then run different daemons in them according to my need (e.g. named, syslogd etc).
To configure my containers I have found it useful to:
i) set the start command to "sh -l" so that it starts a login shell which executes the users .profile.
ii) add /root to the persistent directories under the advanced tab
(this seems to be the default home directory for most stock linux containers).
iii) configure the /root/.profile to contain a short shell script which starts whichever daemons I require from this image.
I would like to be able to configure the /root/.profile in the same way as /etc/network/interfaces (currently selecting the EDIT button from the configuration dialogue allows me to change this).
Allowing /root/.profile to be used like this would have a couple of advantages:
i) I would only need a general purpose image instead of several with minor customisations.
ii) The configuration would be kept in the project rather than in a volume
This would make my projects more portable when exporting them.
Note: So far all the Docker Hub images for linux (that I have tried) have a /root/.profile so what I suggest would certainly work for me.
A more generalised solution would perhaps be to allow the filename to be specified.
The text was updated successfully, but these errors were encountered:
I have been developing quite a few scenarios recently using Docker Containers.
Mostly I use base Linux containers and then run different daemons in them according to my need (e.g. named, syslogd etc).
To configure my containers I have found it useful to:
i) set the start command to "sh -l" so that it starts a login shell which executes the users .profile.
ii) add /root to the persistent directories under the advanced tab
(this seems to be the default home directory for most stock linux containers).
iii) configure the /root/.profile to contain a short shell script which starts whichever daemons I require from this image.
I would like to be able to configure the /root/.profile in the same way as /etc/network/interfaces (currently selecting the EDIT button from the configuration dialogue allows me to change this).
Allowing /root/.profile to be used like this would have a couple of advantages:
i) I would only need a general purpose image instead of several with minor customisations.
ii) The configuration would be kept in the project rather than in a volume
This would make my projects more portable when exporting them.
Note: So far all the Docker Hub images for linux (that I have tried) have a /root/.profile so what I suggest would certainly work for me.
A more generalised solution would perhaps be to allow the filename to be specified.
The text was updated successfully, but these errors were encountered: