8:25 a.m.
Hello,
We build our image based on the Dockerfile with something like
podman build -t sles15-sp6-v73 sles15-sp6-v73
and run it with
podman run -d -p 2022:22 ....sles15-sp6-v73
Building means that based on the Dockerfile we install the software
which should be come up on container start. This works all fine.
When we now add, install or configure something in addition in
the running container, all this gets lost on killing the container
and restart it again with 'podman run...'
Is it somehow possible to write this modified container to an image and
start this again, and not the image which was build with the Dockerfile?
Thanks
matthias
--
Matthias Apitz, ✉ guru(a)unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
8:44 a.m.
Hi Matthias,
On 21/10/2024 14:25, Matthias Apitz wrote:
Hello,
We build our image based on the Dockerfile with something like
podman build -t sles15-sp6-v73 sles15-sp6-v73
and run it with
podman run -d -p 2022:22 ....sles15-sp6-v73
Building means that based on the Dockerfile we install the software
which should be come up on container start. This works all fine.
When we now add, install or configure something in addition in
the running container, all this gets lost on killing the container
and restart it again with 'podman run...'
Is it somehow possible to write this modified container to an image and
start this again, and not the image which was build with the Dockerfile?
yes use podman commit
https://docs.podman.io/en/latest/markdown/podman-commit.1.html
Thanks
matthias
--
Paul Holzinger
3:17 a.m.
El día lunes, octubre 21, 2024 a las 02:44:05 +0200, Paul Holzinger escribió:
Hi Matthias,
yes use podman commit
https://docs.podman.io/en/latest/markdown/podman-commit.1.html
Hi Paul,
After reading the above page and the help of different podman sub
commands, I was able to clone (commit) our container. See the recording
of the various commands below. And the resulting container can be
started fine, SSH'ed into and the software (PostgreSQL server, our
application server, etc.) seems to run fine.
As always, new questions remain:
1)
Why is the old container not found by its image name
"localhost/sles15-sp6-v73:latest"?
2)
What are these 57 (!) repositories with the name "<none>"? Can I just
remove them with "podman rmi ...." based on their IMAGE ID?
3)
I expect that I could also clone (commit) "localhost/sles15-sp6-v73-000"
later to "localhost/sles15-sp6-v73-001", ... , true?
Thanks
matthias
$ podman container list
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS
NAMES
d586c31f5eb8 localhost/sles15-sp6-v73:latest 3 days ago Up 3 days
0.0.0.0:2022->22/tcp, 0.0.0.0:21443->1443/tcp, 0.0.0.0:23045->3045/tcp,
0.0.0.0:28076->8076/tcp jovial_almeida
$ podman commit localhost/sles15-sp6-v73:latest sles15-sp6-v73-000
Error: no container with name or ID "localhost/sles15-sp6-v73:latest" found: no
such container
$ podman commit jovial_almeida sles15-sp6-v73-000
WARN[0028] archive: skipping
"/home/cups/.local/share/containers/storage/overlay/d7fbaae69910272d8b7207d23a110264c30c793ce8a335eea4b6e6a91eff3723/diff/tmp/.s.PGSQL.5432"
since it is a socket
Getting image source signatures
Copying blob af3b0a719a67 skipped: already exists
Copying blob 62d2e4d7b3f8 skipped: already exists
Copying blob 6cfc2baee765 skipped: already exists
...
Copying blob 02102dcad304 skipped: already exists
Copying blob a178d1697ddc skipped: already exists
Copying blob f09d7f8b475a skipped: already exists
Copying blob a7c4c2d4ff39 skipped: already exists
Copying blob 0361dd92970a done |
Copying config 078a42eddc done |
Writing manifest to image destination
078a42eddc7379eba5b0a36b1673c6ec1d582b4088c5ea74cbe63ac91061842a
$ podman> podman image list
REPOSITORY TAG IMAGE ID CREATED SIZE
localhost/sles15-sp6-v73-000 latest 078a42eddc73 5 minutes ago 23.8 GB
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
localhost/sles15-sp6-v73 latest e84f83f1637c 3 days ago 20.2 GB
<none> <none> d3921b019185 3 days ago 18.3
GB
<none> <none> 976bf9911a25 3 days ago 13.7
GB
<none> <none> affda5f588bb 3 days ago 13.6
GB
<none> <none> 7f50df452888 3 days ago 13.6
GB
$ podman run -d -p 2023:22 sles15-sp6-v73-000
160afefea69b168706802d5532f7446c6829eb55c76576e645c34f827308b362
ssh -p 2023 root@localhost
root@localhost's password:
Last login: Tue Oct 22 06:37:45 2024 from 10.0.2.100
160afefea69b:~ #
160afefea69b:~ # /etc/init.d/SunRiseServer_v73 start
SunRiseServer: start SISIS-SunRise servers
Okt 22 06:44:06 DbServer_sisis: OK: start S99avserver (sisis / 8076)
Okt 22 06:44:06 DbServer_sisis: OK: start S99catserver (sisis / 3045)
Okt 22 06:44:06 DbServer_sisis: OK: start S99opserver (sisis / 3025)
Okt 22 06:44:08 DbServer_sisis: OK: start siaddae
Okt 22 06:44:09 DbServer_sisis: OK: start S99z39oserver (sisis / )
Okt 22 06:44:10 DbServer_sisis: OK: start S99sikom
$ podman container list
CONTAINER ID IMAGE COMMAND CREATED STATUS
PORTS
NAMES
d586c31f5eb8 localhost/sles15-sp6-v73:latest 3 days ago Up 3 days
0.0.0.0:2022->22/tcp, 0.0.0.0:21443->1443/tcp, 0.0.0.0:23045->3045/tcp,
0.0.0.0:28076->8076/tcp jovial_almeida
160afefea69b localhost/sles15-sp6-v73-000:latest 10 minutes ago Up 10
minutes 0.0.0.0:2023->22/tcp
xenodochial_ganguly
cups@srap57dxr1:~/sisisbase/podman> podman kill 160afefea69b
160afefea69b
$ podman rm 160afefea69b
160afefea69b
$ podman image list
REPOSITORY TAG IMAGE ID CREATED SIZE
localhost/sles15-sp6-v73-000 latest 078a42eddc73 20 minutes ago 23.8 GB
localhost/sles15-sp6-v73 latest e84f83f1637c 3 days ago 20.2 GB
<none> <none> d3921b019185 3 days ago
18.3 GB
...
$ podman rmi 078a42eddc73
Untagged: localhost/sles15-sp6-v73-000:latest
Deleted: 078a42eddc7379eba5b0a36b1673c6ec1d582b4088c5ea74cbe63ac91061842a
$ podman image list
REPOSITORY TAG IMAGE ID CREATED SIZE
localhost/sles15-sp6-v73 latest e84f83f1637c 3 days ago 20.2 GB
<none> <none> d3921b019185 3 days ago 18.3
GB
<none> <none> 976bf9911a25 3 days ago 13.7
GB
...
$ podman image list | grep '<none>' | wc -l
57
--
Matthias Apitz, ✉ guru(a)unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
101
days inactive
102
days old
2 comments
2 participants
participants (2)
-
Matthias Apitz -
Paul Holzinger