http://jmlj.cas.run pinting at this service.
docker stack deploy -c jmlj.yml jlmjWhere
jmlj.yml is:l
---
version: "3.8"
services:
prologic:
image: r.mills.io/prologic/zs
networks:
- traefik
deploy:
mode: replicated
replicas: 1
labels:
- "traefik.enable=true"
- "traefik.http.services.prologic.loadbalancer.server.port=8000"
resources:
reservations:
memory: 16M
limits:
memory: 32M
restart_policy:
condition: any
networks:
traefik:
external: true
docker stack deploy -c jmlj.yml jlmjWhere
jmlj.yml is:l
---
version: "3.8"
services:
prologic:
image: r.mills.io/prologic/zs
networks:
- traefik
deploy:
mode: replicated
replicas: 1
labels:
- "traefik.enable=true"
- "traefik.http.services.prologic.loadbalancer.server.port=8000"
resources:
reservations:
memory: 16M
limits:
memory: 32M
restart_policy:
condition: any
networks:
traefik:
external: true
docker stack deploy -c jmlj.yml jlmjWhere
jmlj.yml is:l
---
version: "3.8"
services:
prologic:
image: r.mills.io/prologic/zs
networks:
- traefik
deploy:
mode: replicated
replicas: 1
labels:
- "traefik.enable=true"
- "traefik.http.services.prologic.loadbalancer.server.port=8000"
resources:
reservations:
memory: 16M
limits:
memory: 32M
restart_policy:
condition: any
networks:
traefik:
external: true
#pormdn on IRC and this is what they said:
[01:47:58] <Remco> prologic: The podman executable doesn't understand anything docker, but podman does offer a compatibility api for the docker executable. So it would be the second in your or statement
I don't think Podman is compatible with the Docker API, onl the Docker CLI.
#pormdn on IRC and this is what they said:
[01:47:58] <Remco> prologic: The podman executable doesn't understand anything docker, but podman does offer a compatibility api for the docker executable. So it would be the second in your or statement
I don't think Podman is compatible with the Docker API, onl the Docker CLI.
#pormdn on IRC and this is what they said:
[01:47:58] <Remco> prologic: The podman executable doesn't understand anything docker, but podman does offer a compatibility api for the docker executable. So it would be the second in your or statement
I don't think Podman is compatible with the Docker API, onl the Docker CLI.
prologic@JamessMacStudio
Tue Aug 08 01:20:43
~/Projects/docker-proxy
(main) 0 0
$ podman context list
Name URI Identity Default
localhost tcp://localhost:2376 true
prologic@JamessMacStudio
Tue Aug 08 01:20:57
~/Projects/docker-proxy
(main) 0
$ podman --help | grep id
--identity string path to SSH identity file, (CONTAINER_SSHKEY)
I was never able to get the SSH version of the intercepting proxy working. I spent a couple of years on/off trying to get it to work, but there are limitations with the standard library and/or the ssh library or something that prevented the SSH Proxy from fully working See Issue #2 which I've now closed as "won't fix".
I guess Podman needs to learn how to do TLS?
prologic@JamessMacStudio
Tue Aug 08 01:20:43
~/Projects/docker-proxy
(main) 0 0
$ podman context list
Name URI Identity Default
localhost tcp://localhost:2376 true
prologic@JamessMacStudio
Tue Aug 08 01:20:57
~/Projects/docker-proxy
(main) 0
$ podman --help | grep id
--identity string path to SSH identity file, (CONTAINER_SSHKEY)
I was never able to get the SSH version of the intercepting proxy working. I spent a couple of years on/off trying to get it to work, but there are limitations with the standard library and/or the ssh library or something that prevented the SSH Proxy from fully working See Issue #2 which I've now closed as "won't fix".
I guess Podman needs to learn how to do TLS?
prologic@JamessMacStudio
Tue Aug 08 01:20:43
~/Projects/docker-proxy
(main) 0 0
$ podman context list
Name URI Identity Default
localhost tcp://localhost:2376 true
prologic@JamessMacStudio
Tue Aug 08 01:20:57
~/Projects/docker-proxy
(main) 0
$ podman --help | grep id
--identity string path to SSH identity file, (CONTAINER_SSHKEY)
I was never able to get the SSH version of the intercepting proxy working. I spent a couple of years on/off trying to get it to work, but there are limitations with the standard library and/or the ssh library or something that prevented the SSH Proxy from fully working See Issue #2 which I've now closed as "won't fix".
I guess Podman needs to learn how to do TLS?
$ sh setup.sh
Error: --docker additional options "ca=/Users/prologic/.docker/certs.d/localhost/ca.pem,key=/Users/prologic/.docker/certs.d/localhost/key.pem,cert=/Users/prologic/.docker/certs.d/localhost/cert.pem" not supported
Not support for TLS?
$ sh setup.sh
Error: --docker additional options "ca=/Users/prologic/.docker/certs.d/localhost/ca.pem,key=/Users/prologic/.docker/certs.d/localhost/key.pem,cert=/Users/prologic/.docker/certs.d/localhost/cert.pem" not supported
Not support for TLS?
$ sh setup.sh
Error: --docker additional options "ca=/Users/prologic/.docker/certs.d/localhost/ca.pem,key=/Users/prologic/.docker/certs.d/localhost/key.pem,cert=/Users/prologic/.docker/certs.d/localhost/cert.pem" not supported
Not support for TLS?
root@proxy:~# ls -lah /usr/bin/docker /usr/bin/dockerd
-rwxr-xr-x 1 root root 35M Jul 21 20:35 /usr/bin/docker
-rwxr-xr-x 1 root root 96M Jul 21 20:35 /usr/bin/dockerd
root@proxy:~#
Compared with Podman:
$ ls -lah /opt/homebrew/Cellar/podman/4.6.0/bin/podman-remote
-r-xr-xr-x 1 prologic admin 39M Jul 21 06:13 /opt/homebrew/Cellar/podman/4.6.0/bin/podman-remote
As you can see the Docker
docker client (CLI) and the Podman tool is roughly the same "weight".The difference is that Docker is a Server<->Client with a daemon architecture, whereas Podman runs containers directly, which is why only Linux is supported. Podman is a bit like my box project.~
root@proxy:~# ls -lah /usr/bin/docker /usr/bin/dockerd
-rwxr-xr-x 1 root root 35M Jul 21 20:35 /usr/bin/docker
-rwxr-xr-x 1 root root 96M Jul 21 20:35 /usr/bin/dockerd
root@proxy:~#
Compared with Podman:
$ ls -lah /opt/homebrew/Cellar/podman/4.6.0/bin/podman-remote
-r-xr-xr-x 1 prologic admin 39M Jul 21 06:13 /opt/homebrew/Cellar/podman/4.6.0/bin/podman-remote
As you can see the Docker
docker client (CLI) and the Podman tool is roughly the same "weight".The difference is that Docker is a Server<->Client with a daemon architecture, whereas Podman runs containers directly, which is why only Linux is supported. Podman is a bit like my box project.~
root@proxy:~# ls -lah /usr/bin/docker /usr/bin/dockerd
-rwxr-xr-x 1 root root 35M Jul 21 20:35 /usr/bin/docker
-rwxr-xr-x 1 root root 96M Jul 21 20:35 /usr/bin/dockerd
root@proxy:~#
Compared with Podman:
$ ls -lah /opt/homebrew/Cellar/podman/4.6.0/bin/podman-remote
-r-xr-xr-x 1 prologic admin 39M Jul 21 06:13 /opt/homebrew/Cellar/podman/4.6.0/bin/podman-remote
As you can see the Docker
docker client (CLI) and the Podman tool is roughly the same "weight".The difference is that Docker is a Server<->Client with a daemon architecture, whereas Podman runs containers directly, which is why only Linux is supported. Podman is a bit like my box project.~
> I ran some containers using podman and I think they are running remotely but I donβt know the right juju to verify. It looks right though!
Let me check...
> I ran some containers using podman and I think they are running remotely but I donβt know the right juju to verify. It looks right though!
Let me check...
> I ran some containers using podman and I think they are running remotely but I donβt know the right juju to verify. It looks right though!
Let me check...
alias docker=podman, but cannot use podman as a "client" to a remote Docker API engine π’
alias docker=podman, but cannot use podman as a "client" to a remote Docker API engine π’
alias docker=podman, but cannot use podman as a "client" to a remote Docker API engine π’
https://cas.run/
https://cas.run/
https://cas.run/
docker CLI. You don't obviously need to have anything else but the CLI to use it as the containers are running remote form you. The install of the CLi is pretty quick 'n easy on most (_if not all?_) systems._
docker CLI. You don't obviously need to have anything else but the CLI to use it as the containers are running remote form you. The install of the CLi is pretty quick 'n easy on most (_if not all?_) systems._
docker CLI. You don't obviously need to have anything else but the CLI to use it as the containers are running remote form you. The install of the CLi is pretty quick 'n easy on most (_if not all?_) systems._
https://github.com/${GITHUB_USER}.keys return keys for you? That's what its using to do auth right now.
https://github.com/${GITHUB_USER}.keys return keys for you? That's what its using to do auth right now.
https://github.com/${GITHUB_USER}.keys return keys for you? That's what its using to do auth right now.
- https://twtxt.net/twt/bjdy5ea
- https://twtxt.net/twt/fjwkpxa
- https://twtxt.net/twt/aqahq5a
There is duplicate entry here with slightly different content, but not much we can do about that π
- https://twtxt.net/twt/bjdy5ea
- https://twtxt.net/twt/fjwkpxa
- https://twtxt.net/twt/aqahq5a
There is duplicate entry here with slightly different content, but not much we can do about that π
- https://twtxt.net/twt/bjdy5ea
- https://twtxt.net/twt/fjwkpxa
- https://twtxt.net/twt/aqahq5a
There is duplicate entry here with slightly different content, but not much we can do about that π
podman "just works"β’ awesome π
podman "just works"β’ awesome π
podman "just works"β’ awesome π
> Podman commands are fully compatible with Docker, so you can replace one with the other: alias docker=podman . The core Podman runtime environment can only run on Linux operating systems. However, you can use a remote client for other operating systems to manage containers on the machine running Podman.12 Apr 2023=
> Podman commands are fully compatible with Docker, so you can replace one with the other: alias docker=podman . The core Podman runtime environment can only run on Linux operating systems. However, you can use a remote client for other operating systems to manage containers on the machine running Podman.12 Apr 2023=
> Podman commands are fully compatible with Docker, so you can replace one with the other: alias docker=podman . The core Podman runtime environment can only run on Linux operating systems. However, you can use a remote client for other operating systems to manage containers on the machine running Podman.12 Apr 2023=
podman compatible and uses the same Docker API? π€ I'm not sure myself.In terms of breaking it, yes please, by all means, do try and of course let me know. I'm not sure how good any of this is just yet... Still seeing what's possible. I'm actually trying to set-up some ingress and default routing so folks _could_ host simple stuff. Tricky to get right π
podman compatible and uses the same Docker API? π€ I'm not sure myself.In terms of breaking it, yes please, by all means, do try and of course let me know. I'm not sure how good any of this is just yet... Still seeing what's possible. I'm actually trying to set-up some ingress and default routing so folks _could_ host simple stuff. Tricky to get right π
podman compatible and uses the same Docker API? π€ I'm not sure myself.In terms of breaking it, yes please, by all means, do try and of course let me know. I'm not sure how good any of this is just yet... Still seeing what's possible. I'm actually trying to set-up some ingress and default routing so folks _could_ host simple stuff. Tricky to get right π
ssh -p 2222 cas.run help
ssh -p 2222 cas.run help
ssh -p 2222 cas.run help