M'm having an issue with a growing data file that is getting too large in my centos7 server. Links to similar issues i've seen: https://github.com/docker/docker/issues/3182
This link suggests stopping docker, deleting the data file and turning back on docker: Why is docker image eating up my disk space that is not used by docker
Will deleting the data loop file destroy my existing container data? Or images? What does this file do?
I can also add more diskspace to this server, but it seems like padding the issue instead of solving whats going on:
Docker Version:
Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8
OS/Arch (client): linux/amd64
Server version: 1.4.1
Server API version: 1.16
Go version (server): go1.3.3
Related
Versions of Docker tooling:
Docker Compose version v2.6.0
Docker Engine Version 20.10.17 (client)
Docker Engine Version 20.10.17 (server)
I've got a compose file that starts a swarm with networks and secrets, so I'm using Docker Compose File Version 3.9.
One of my services is a GPU resource, so I added this based on current docs:
version: "3.9"
services:
my-app:
image: my-app:latest
deploy:
resources:
reservations:
devices:
- capabilities: [gpu]
count: all
. . .
My IDE is complaining with "expected scalar value" indicating that it doesn't recognize the key or value of capabilities and count and when I run the command:
docker stack deploy --compose-file docker-compose.yml my-stack
Docker throws an error:
services.prosit-app.deploy.resources.reservations Additional property devices is not allowed
Based on the versions of my Docker tools and the schema I'm using, this should all work (I think). What am missing?
I've tried various file versions and I can get the IDE warning to go away but then Docker can't support the file version. I've tried with and without quotes ["gpu"], different options, etc, to no avail.
This question was asked already (my bad) and the answer was missed by me and others:
Docker Compose returns error about property devices when trying to enable GPU
Reference:
https://docs.docker.com/compose/compose-file/compose-file-v3/#devices
I recently updated minishift on mac:
minishift update:
...
Starting OpenShift using openshift/origin:v3.6.1 ...
..
-- Finding server IP ...
...
FAIL
Error: could not start OpenShift container "origin"
Details:
No log available from "origin" container
Error during 'cluster up' execution: Error starting the cluster.
$ minishift version
minishift v1.12.0+daa0943
There is an issue with v3.6.1.
If I revert back to v3.6.0 with:
brew cask reinstall minishift
OR
minishift start --openshift-version=v3.6.0
With version v3.6.0, it works it and does not do Finding server IP ...
Please advise how to fix v3.6.1 issue with:
No log available from "origin" container
It seems you already had a Minishift instance which was in stopped state when you ran the update command. Because the newer version has v3.6.1 as the default OpenShift version you are seeing this issue. Minsihift recommends [1] deleting the current instance and then starting will fix the issue.
[1] https://docs.openshift.org/latest/minishift/getting-started/updating.html#update-instructions
Minishift is hosted within a VM. Currently, this VM is replaced entirely on upgrade.
Have you considered trying the cluster backup and restore features?: https://docs.openshift.org/latest/admin_guide/backup_restore.html
i'm new to docker. I run docker "natively" from a Windows server 2016 with a Windows container, there is no intermediate VM (no docker machine) in between and no docker toolbox, so the "host" is the actual Windows Server that I run docker on.
Docker version:
PS C:> docker version
Client:
Version: 17.03.1-ee-3
API version: 1.27
Go version: go1.7.5
Git commit: 3fcee33
Built: Thu Mar 30 19:31:22 2017
OS/Arch: windows/amd64
Server:
Version: 17.03.1-ee-3
API version: 1.27 (minimum version 1.24)
Go version: go1.7.5
Git commit: 3fcee33
Built: Thu Mar 30 19:31:22 2017
OS/Arch: windows/amd64
Experimental: false
PS C:>
i pulled the image from docker hub. I need to replace the files inside the docker image while running and commit changes to the image.
Lets say i have Sample.java and datafile.properties inside the docker image which i pulled from docker hub.
i want to replace that with Hello.java and data.properties[ i pulled these files from github]
how would i do that in an automated way? Any advise and some examples on this would he helpful. Thanks in advance.
The best way to build an image automated, is to use a Dockerfile. Some information can be found in the documentation, for example; https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/
If you have your Hello.java and datafile.properties in a directory, create a Dockerfile in the same directory, e.g.;
FROM the-base-image-on-docker-hub
RUN rm /path/to/Sample.java
COPY ./Hello.java /path/to/
COPY ./datafile.properties /path/to/
You can then build your image, and "tag" it as myimage:latest with;
docker image build -t myimage:latest .
(the period at the end (.) indicates; use the current directory as "build context" - the build context is uploaded to the docker daemon, and everything in it will be accessible to add to your docker image using the COPY or ADD Dockerfile instructions)
This is a very naive example, just to illustrate the concept; I suggest reading the documentation, to understand the concept, and searching for more examples.
Rocket.Chat Version: 0.56.0-develop
Running Instances: 1
DB Replicaset OpLog: Enabled
Node Version: v4.8.1
I cloned the git code and started rocket chat in my local machine Windods 7 by following instructions as bellow.
git clone https://github.com/RocketChat/Rocket.Chat.git
cd Rocket.Chat
meteor npm start
Now, I want during development my app to use my local mongoDB installation instead of meteors's internal. I tried a lot but did not get any help or clue. It seems I am missing somewhere. I attaching the screen of what I changed, I hope I am doing the right. I did changed in docker-compose.yml.
I found such command as docker-compose down on docker website, but when I try to use it i get an error.
No such command: down
Commands:
build Build or rebuild services
help Get help on a command
kill Kill containers
logs View output from containers
port Print the public port for a port binding
ps List containers
pull Pulls service images
restart Restart services
rm Remove stopped containers
run Run a one-off command
scale Set number of containers for a service
start Start services
stop Stop services
up Create and start containers
migrate-to-labels Recreate containers to add labels
My docker-compose version is:
docker-compose version: 1.3.1
CPython version: 2.7.10
OpenSSL version: OpenSSL 1.0.2d 9 Jul 2015
Did I do something wrong?
It might be that docker-compose down command is not available in the version you use - the command was added in version 1.6.0 - see the CHANGELOG here.
So if you really want to use the command, you may have to upgrade to version 1.6.0 or later.
Hope this helps.